Devices, systems and methods for a cloud-based meter management system

ABSTRACT

Devices, systems and methods for a cloud-based meter management system are provided. The present disclosure includes a meter cloud server, a plurality of IEDs or meters, and one or more clients 608 (e.g., a web browser client), which are coupled together via a network (e.g., via various wireless and/or hardwired communication networks). The various components and modules of the present disclosure provide a plurality of functions to enable one or more users to manage a plurality of IEDs or meters via the at least one client device.

PRIORITY

This application claims priority to U.S. Provisional Patent ApplicationSer. No. 62/752,740, filed Oct. 30, 2018, the contents of which arehereby incorporated by reference in its entirety.

This application also claims priority to U.S. Provisional PatentApplication Ser. No. 62/869,532, filed Jul. 1, 2019, the contents ofwhich are hereby incorporated by reference in its entirety.

This application is also a continuation-in-part application to U.S.patent application Ser. No. 16/278,760, filed Feb. 19, 2019, whichclaims priority to U.S. Provisional Patent Application Ser. Nos.62/631,660, filed Feb. 17, 2018, and 62/752,740, filed Oct. 30, 2018,the contents of which are hereby incorporated by reference in theirentireties.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is related to

-   -   U.S. patent application Ser. No. 13/644,877, filed Oct. 4, 2012,    -   U.S. patent application Ser. No. 13/799,832, filed Mar. 13,        2013,    -   U.S. patent application Ser. No. 13/836,671, filed Mar. 15,        2013,    -   U.S. patent application Ser. No. 14/742,302, filed Jun. 17,        2015,        the contents of each of the above listed applications are hereby        incorporated by reference in their entirety.

BACKGROUND Field

The present disclosure relates generally to intelligent electronicdevices (IEDs) and, in particular, to devices, systems and methods for acloud-based meter management system.

Description of the Related Art

Monitoring of electrical energy by consumers and providers of electricpower is a fundamental function within any electric power distributionsystem. Electrical energy may be monitored for purposes of usage,equipment performance and power quality. Electrical parameters that maybe monitored include volts, amps, watts, vars, power factor, harmonics,kilowatt hours, kilovar hours and any other power related measurementparameters. Typically, measurement of the voltage and current at alocation within the electric power distribution system may be used todetermine the electrical parameters for electrical energy flowingthrough that location.

Devices that perform monitoring of electrical energy may beelectromechanical devices, such as, for example, a residential billingmeter or may be an intelligent electronic device (“TED”). Intelligentelectronic devices typically include some form of a processor. Ingeneral, the processor is capable of using the measured voltage andcurrent to derive the measurement parameters. The processor operatesbased on a software configuration. A typical consumer or supplier ofelectrical energy may have many intelligent electronic devices installedand operating throughout their operations. TEDs may be positioned alongthe supplier's distribution path or within a customer's internaldistribution system. TEDs include revenue electric watt-hour meters,protection relays, programmable logic controllers, remote terminalunits, fault recorders and other devices used to monitor and/or controlelectrical power distribution and consumption. TEDs are widely availablethat make use of memory and microprocessors to provide increasedversatility and additional functionality. Such functionality includesthe ability to communicate with remote computing systems, either via adirect connection, e.g., a modem, a wireless connection or a network.TEDs also include legacy mechanical or electromechanical devices thathave been retrofitted with appropriate hardware and/or software allowingintegration with the power management system.

Typically, an TED is associated with a particular load or set of loadsthat are drawing electrical power from the power distribution system.The TED may also be capable of receiving data from or controlling itsassociated load. Depending on the type of TED and the type of load itmay be associated with, the TED implements a power management functionthat is able to respond to a power management command and/or generatepower management data. Power management functions include measuringpower consumption, controlling power distribution such as a relayfunction, monitoring power quality, measuring power parameters such asphasor components, voltage or current, controlling power generationfacilities, computing revenue, controlling electrical power flow andload shedding, or combinations thereof.

SUMMARY

In accordance with embodiments of the present disclosure, there areprovided herein devices, methods and systems for a cloud-based metermanagement system. The cloud-based meter management system of thepresent disclosure enables one or more client devices to seamlessly andefficiently manage a plurality of meters or intelligent electronicdevices (IEDs) disposed throughout various locations.

In one embodiment, a cloud-based meter management system is providedincluding at least one meter manager module that collects meter log datafrom at least one meter and sends the collected meter log data to atleast one server via a predetermined format; the at least one serverreceives and stores the collected meter log data from the at least onemeter manager module; and at least one client device that accesses theat least one server to view the meter log data.

In one aspect, the system further includes at least one network enabledmeter that sends meter log data to the at least one server via thepredetermined format.

In another aspect, the predetermined format is JSON data format.

In a further aspect, the predetermined format is at least of a XMLand/or HTML.

In yet another aspect, the at least one server includes a web server forproviding a user interface to the at least one client device.

In one aspect, the at least one server includes at least one REST webservice that receives at least one request from the at least one clientdevice and provide a response to the at least one request.

In another aspect, the at least one REST web service further receivesthe collected meter log data from the at least one meter manager modulefor storage in at least one database.

In still another aspect, the at least one server is configured forautoscaling to add at least one additional server when an increased loadof data sent to the at least one server exceeds a predetermined limit.

In another aspect, the system further includes at least one loadbalancer for distributing the sent data among the at least one serverand the at least one additional server.

In a further aspect, the system further includes a message broker forrouting communications between the at least one web server, the at leastREST web service and the at least one database.

In another aspect of the present disclosure, the system further includesat least one consumer that performs at least one of collecting callsfrom the at least one REST web service, sending the calls to the atleast one database and/or returning data from the at least one database.

In one aspect, the at least one consumer includes a push consumer thatcaptures sent data from the message broker and stores the sent data inthe at least one database.

In another aspect, the at least one consumer includes a metadataconsumer that receives at least one request from the message broker,sends the at least one request to the at least one database and sends atleast one response for presentation on a web site hosted by the at leastone server.

In still another aspect, the at least one server generates a key uponregistration of a user, wherein the generated key is associated to theat least one meter of the registered user.

In a further aspect, the at least one server verifies the sent datareceived from the at least one meter via the generated key.

In yet another aspect, the at least one server determines if the sentmeter log data from the at least one meter manager module exceeds apredetermined limit and, if the predetermined limit is exceeded, the atleast one server excludes the data from being stored in the at least onedatabase.

In one aspect, the at least one server records a count and associatedtime of day when the data was excluded.

In another aspect, the at least one server presents the count andassociated time of day of the excluded data to at least one user via aweb page.

In a further aspect, the meter log data includes waveform data, thewaveform data including at least one of Trigger Cause, Trigger Time,Recording Start Time, Time per sample, Total duration, Samples percycle, List of samples per channel and/or List of RMS values for thecycle at the time of the trigger, and the at least one server is furtherconfigured send a single waveform recording to the at least one clientdevice in response to a query.

According to another aspect of the present disclosure, a cloud-basedmeter management system includes at least one web service enabled meterthat pushes meter log data to at least one server via a predeterminedformat; at least one meter manager module that collects meter log datafrom at least one non-web service meter and pushes the collected meterlog data to the at least one server via the predetermined format; the atleast one server receives and stores pushed meter log data from the atleast one web service enabled meter and the collected meter log datafrom the at least one meter manager module; and at least one clientdevice that accesses the at least one server to view the meter log data.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other objects, features and advantages of the presentdisclosure will be apparent from a consideration of the followingDetailed Description considered in conjunction with the drawing Figures,in which:

FIG. 1 is a block diagram of an intelligent electronic device (IED),according to an embodiment of the present disclosure.

FIGS. 2A-2H illustrate exemplary form factors for an intelligentelectronic device (IED) in accordance with an embodiment of the presentdisclosure.

FIG. 3 illustrates an environment in which the present disclosure may beutilized.

FIG. 4 is a functional block diagram of a processor of an intelligentelectronic device according to the embodiment of the present disclosure.

FIG. 5 illustrates another environment in which the present disclosuremay be utilized.

FIG. 6 illustrates a cloud-based meter management system in accordancewith the present disclosure.

FIG. 7 illustrates components of the cloud-based meter management systemshown in FIG. 6.

FIG. 8 illustrates components of the local area network (LAN) shown inFIG. 7.

FIG. 9 illustrates a network configuration of a server of thecloud-based meter management system in accordance with the presentdisclosure.

FIG. 10 is a user login flow diagram in accordance with the presentdisclosure.

FIG. 11 is a meter registration flow diagram in accordance with thepresent disclosure.

FIG. 12 illustrates an overview of an interaction between a clientsoftware and cloud server in accordance with the present disclosure.

FIG. 13 illustrates a functional block diagram of a meter manager modulein accordance with the present disclosure.

FIG. 14 is a log service flow diagram in accordance with the presentdisclosure.

FIG. 15 is a cloud upload service diagram in accordance with the presentdisclosure.

FIG. 16 is a WebAPI RPC flow diagram in accordance with the presentdisclosure.

FIG. 17 is a user interface flow diagram in accordance with the presentdisclosure.

FIG. 18 is a log viewer flow diagram in accordance with the presentdisclosure.

FIG. 19 is a cloud viewer flow diagram in accordance with the presentdisclosure.

FIG. 20 illustrates a user interface interaction between a client deviceand a cloud server in accordance with the present disclosure.

FIG. 21 is a flow diagram for registering a cloud ID and syncing thecloud ID with the cloud server in accordance with the presentdisclosure.

FIG. 22 illustrates interactions of the meter manager monitor, metermanager service and a cloud server in accordance with the presentdisclosure.

FIG. 23 illustrates a cloud sync service in accordance with the presentdisclosure.

FIG. 24 is a flow diagram of a meter registration process using a key inaccordance with the present disclosure.

FIG. 25 is a flow diagram of a meter registration process by searchingUID or serial number in accordance with the present disclosure.

FIG. 26 illustrates an overview of user management of the cloud-basedmeter management system is a flow diagram of a meter registrationprocess using a key in accordance with the present disclosure.

FIG. 27 illustrates a graphical representation of waveform data inaccordance with the present disclosure.

FIG. 28 is a flow diagram of a limitor notification in accordance withthe present disclosure.

FIG. 29 illustrates an energy billing module in accordance with thepresent disclosure.

FIG. 30 is a payment system for customer usage flow diagram inaccordance with the present disclosure.

FIG. 31 illustrates an overview of a user interface for the cloud-basedmeter management system in accordance with the present disclosure.

FIG. 32 is a block diagram of an exemplary computing device inaccordance with an embodiment of the present disclosure.

FIG. 33 is a flow diagram illustrating a method for pushing data to acloud server in accordance with the present disclosure.

FIG. 34 is a flow diagram illustrating a method for handling varioustypes of data in accordance with the present disclosure.

FIG. 35 is a flow diagram illustrating a method for interacting with acloud server in accordance with the present disclosure.

FIG. 36 illustrates a heatmap of energy usage for a meter in accordancewith the present disclosure.

DETAILED DESCRIPTION

Embodiments of the present disclosure will be described herein belowwith reference to the accompanying drawings. In the followingdescription, well-known functions or constructions are not described indetail to avoid obscuring the present disclosure in unnecessary detail.The word “exemplary” is used herein to mean “serving as an example,instance, or illustration.” Any configuration or design described hereinas “exemplary” is not necessarily to be construed as preferred oradvantageous over other configurations or designs. Herein, the phrase“coupled” is defined to mean directly connected to or indirectlyconnected with through one or more intermediate components. Suchintermediate components may include both hardware and software basedcomponents.

It is further noted that, unless indicated otherwise, all functionsdescribed herein may be performed in either hardware or software, orsome combination thereof. In one embodiment, however, the functions areperformed by at least one processor, such as a computer or an electronicdata processor, digital signal processor or embedded micro-controller,in accordance with code, such as computer program code, software, and/orintegrated circuits that are coded to perform such functions, unlessindicated otherwise.

It should be appreciated that the present disclosure can be implementedin numerous ways, including as a process, an apparatus, a system, adevice, a method, or a computer readable medium such as a computerreadable storage medium or a computer network where program instructionsare sent over optical or electronic communication links. Additionally,it is to be appreciated that in the drawings any line connectingcomponents, devices, method steps, blocks, etc. that is illustrated as asingle headed arrow, i.e., to indicate one way direction, may beinterchangeable and/or replaced with a double headed arrow, i.e., toindicate two-way direction.

Embodiments of the present disclosure will be described herein belowwith reference to the accompanying drawings.

As used herein, intelligent electronic devices (“IEDs”) can be anydevice that senses electrical parameters and computes data including,but not limited to, Programmable Logic Controllers (“PLC's”), RemoteTerminal Units (“RTU's”), electric power meters, panel meters,protective relays, fault recorders, phase measurement units, serialswitches, smart input/output devices and other devices which are coupledwith power distribution networks to manage and control the distributionand consumption of electrical power. A meter is a device that recordsand measures power events, power quality, current, voltage waveforms,harmonics, transients and other power disturbances. Revenue accuratemeters (“revenue meter”) relate to revenue accuracy electrical powermetering devices with the ability to detect, monitor, report, quantifyand communicate power quality information about the power that they aremetering.

FIG. 1 is a block diagram of an intelligent electronic device (IED) 10for monitoring and determining power usage and power quality for anymetered point within a power distribution system and for providing adata transfer system for faster and more accurate processing of revenueand waveform analysis.

The IED 100 of FIG. 1 includes a plurality of sensors 112 coupled tovarious phases A, B, C and neutral N of an electrical distributionsystem 111, a plurality of analog-to-digital (A/D) converters 114,including inputs coupled to the sensor 112 outputs, a power supply 116,a volatile memory 118, an non-volatile memory 120, a multimedia userinterface 122, and a processing system that includes at least onecentral processing unit (CPU) 150 (or host processor) and/or one or moredigital signal processors, two of which are shown, i.e., DSP1 160 andDSP2 170. The IED 100 also includes a Field Programmable Gate Array 180which performs a number of functions, including, but not limited to,acting as a communications gateway for routing data between the variousprocessors 150, 160, 170, receiving data from the A/D converters 114performing transient detection and capture and performing memorydecoding for CPU 150 and the DSP processor 160. In one embodiment, theFPGA 80 is internally comprised of two dual port memories to facilitatethe various functions. It is to be appreciated that the variouscomponents shown in FIG. 1 are contained within housing 190. Exemplaryhousings will be described below in relation to FIGS. 2A-2H.

The plurality of sensors 112 sense electrical parameters, e.g., voltageand current, on incoming lines (i.e., phase A, phase B, phase C, neutralN) of an electrical power distribution system 111 e.g., an electricalcircuit, that are coupled to at least one load 113 that consumes thepower provided. In one embodiment, the sensors 112 will include currenttransformers and potential transformers, wherein one current transformerand one voltage transformer will be coupled to each phase of theincoming power lines. A primary winding of each transformer will becoupled to the incoming power lines and a secondary winding of eachtransformer will output a voltage representative of the sensed voltageand current. The output of each transformer will be coupled to the A/Dconverters 114 configured to convert the analog output voltage from thetransformer to a digital signal that can be processed by the CPU 150,DSP1 160, DSP2 170, FPGA 180 or any combination thereof.

A/D converters 114 are respectively configured to convert an analogvoltage output to a digital signal that is transmitted to a gate array,such as Field Programmable Gate Array (FPGA) 180. The digital signal isthen transmitted from the FPGA 180 to the CPU 150 and/or one or more DSPprocessors 160, 170 to be processed in a manner to be described below.

The CPU 150 or DSP Processors 160, 170 are configured to operativelyreceive digital signals from the A/D converters 114 (see FIG. 1) toperform calculations necessary to determine power usage and to controlthe overall operations of the IED 100. In some embodiments, CPU 150,DSP1 160 and DSP2 170 may be combined into a single processor, servingthe functions of each component. In some embodiments, it is contemplatedto use an Erasable Programmable Logic Device (EPLD) or a ComplexProgrammable Logic Device (CPLD) or any other programmable logic devicein place of the FPGA 180. In some embodiments, the digital samples,which are output from the A/D converters 114 are sent directly to theCPU 150 or DSP processors 160, 170, effectively bypassing the FPGA 180as a communications gateway.

The power supply 116 provides power to each component of the IED 100. Inone embodiment, the power supply 116 is a transformer with its primarywindings coupled to the incoming power distribution lines and havingwindings to provide a nominal voltage, e.g., 5 VDC, +12 VDC and −12 VDC,at its secondary windings. In other embodiments, power may be suppliedfrom an independent power source to the power supply 116. For example,power may be supplied from a different electrical circuit or anuninterruptible power supply (UPS).

In one embodiment, the power supply 116 can be a switch mode powersupply in which the primary AC signal will be converted to a form of DCsignal and then switched at high frequency, such as, for example, 100Khz, and then brought through a transformer to step the primary voltagedown to, for example, 5 Volts AC. A rectifier and a regulating circuitwould then be used to regulate the voltage and provide a stable DC lowvoltage output. Other embodiments, such as, but not limited to, linearpower supplies or capacitor dividing power supplies are alsocontemplated.

The multimedia user interface 122 is shown coupled to the CPU 150 inFIG. 1 for interacting with a user and for communicating events, such asalarms and instructions to the user. The multimedia user interface 122may include a display for providing visual indications to the user. Thedisplay may be embodied as a touch screen, a liquid crystal display(LCD), a plurality of LED number segments, individual light bulbs or anycombination. The display may provide information to the user in the formof alpha-numeric lines, computer-generated graphics, videos, animations,etc. The multimedia user interface 122 further includes a speaker oraudible output means for audibly producing instructions, alarms, data,etc. The speaker is coupled to the CPU 150 via a digital-to-analogconverter (D/A) for converting digital audio files stored in a memory118 or non-volatile memory 120 to analog signals playable by thespeaker. An exemplary interface is disclosed and described in commonlyowned U.S. Pat. No. 8,442,660, entitled “POWER METER HAVING AUDIBLE ANDVISUAL INTERFACE”, which claims priority to expired U.S. ProvisionalPatent Appl. No. 60/731,006, filed Oct. 28, 2005, the contents of whichare hereby incorporated by reference in their entireties.

The IED 100 will support various file types including but not limited toMicrosoft Windows Media Video files (.wmv), Microsoft Photo Story files(.asf), Microsoft Windows Media Audio files (.wma), MP3 audio files(.mp3), JPEG image files (.jpg, .jpeg, .jpe, .jfif), MPEG movie files(.mpeg, .mpg, .mpe, .m1v, .mp2v .mpeg2), Microsoft Recorded TV Showfiles (.dvr-ms), Microsoft Windows Video files (.avi) and MicrosoftWindows Audio files (.wav).

The IED 100 further comprises a volatile memory 118 and a non-volatilememory 120. In addition to storing audio and/or video files, volatilememory 118 will store the sensed and generated data for furtherprocessing and for retrieval when called upon to be displayed at the IED100 or from a remote location. The volatile memory 118 includes internalstorage memory, e.g., random access memory (RAM), and the non-volatilememory 120 includes removable memory such as magnetic storage memory;optical storage memory, e.g., the various types of CD and DVD media;solid-state storage memory, e.g., a CompactFlash card, a Memory Stick,SmartMedia card, MultiMediaCard (MMC), SD (Secure Digital) memory; orany other memory storage that exists currently or will exist in thefuture. By utilizing removable memory, an IED can be easily upgraded asneeded. Such memory will be used for storing historical trends, waveformcaptures, event logs including time-stamps and stored digital samplesfor later downloading to a client application, web-server or PCapplication.

In a further embodiment, the IED 100 will include a communication device124, also know as a network interface, for enabling communicationsbetween the IED or meter, and a remote terminal unit, programmable logiccontroller and other computing devices, microprocessors, a desktopcomputer, laptop computer, other meter modules, etc. The communicationdevice 124 may be a modem, network interface card (NIC), wirelesstransceiver, etc. The communication device 124 will perform itsfunctionality by hardwired and/or wireless connectivity. The hardwireconnection may include but is not limited to hard wire cabling e.g.,parallel or serial cables, RS232, RS485, USB cable, Firewire (1394connectivity) cables, Ethernet, and the appropriate communication portconfiguration. The wireless connection may operate under any of thevarious wireless protocols including but not limited to Bluetooth™interconnectivity, infrared connectivity, radio transmissionconnectivity including computer digital signal broadcasting andreception commonly referred to as Wi-Fi or 802.11.X (where x denotes thetype of transmission), satellite transmission or any other type ofcommunication protocols, communication architecture or systems currentlyexisting or to be developed for wirelessly transmitting data includingspread spectrum 900 MHz, or other frequencies, Zigbee, WiFi, or any meshenabled wireless communication.

The IED 100 may communicate to a server or other computing device viathe communication device 124. The IED 100 may be connected to acommunications network, e.g., the Internet, by any means, for example, ahardwired or wireless connection, such as dial-up, hardwired, cable,DSL, satellite, cellular, PCS, wireless transmission (e.g.,802.11a/b/g), etc.. It is to be appreciated that the network may be alocal area network (LAN), wide area network (WAN), the Internet or anynetwork that couples a plurality of computers to enable various modes ofcommunication via network messages. Furthermore, the server willcommunicate using various protocols such as Transmission ControlProtocol/Internet Protocol (TCP/IP), File Transfer Protocol (FTP),Hypertext Transfer Protocol (HTTP), etc. and secure protocols such asHypertext Transfer Protocol Secure (HTTPS), Internet Protocol SecurityProtocol (IPSec), Point-to-Point Tunneling Protocol (PPTP), SecureSockets Layer (SSL) Protocol, etc. The server may further include astorage medium for storing a data received from at least one IED ormeter and/or storing data to be retrieved by the IED or meter.

In an additional embodiment, the IED 100 may also have the capability ofnot only digitizing waveforms, but storing the waveform and transferringthat data upstream to a central computer, e.g., a remote server, when anevent occurs such as a voltage surge or sag or a current short circuit.This data may be triggered and captured on an event, stored to memory,e.g., non-volatile RAM, and additionally transferred to a host computerwithin the existing communication infrastructure either immediately inresponse to a request from a remote device or computer to receive saiddata in response to a polled request. The digitized waveform will alsoallow the CPU 150 to compute other electrical parameters such asharmonics, magnitudes, symmetrical components and phasor analysis. Usingthe harmonics, the IED 100 will also calculate dangerous heatingconditions and can provide harmonic transformer derating based onharmonics found in the current waveform.

In a further embodiment, the IED 100 will execute an e-mail client andwill send e-mails to the utility or to the customer direct on anoccasion that a power quality event occurs. This allows utilitycompanies to dispatch crews to repair the condition. The data generatedby the meters are used to diagnose the cause of the condition. The datais transferred through the infrastructure created by the electricalpower distribution system. The email client will utilize a POP3 or otherstandard mail protocol. A user will program the outgoing mail server andemail address into the meter. An exemplary embodiment of said meteringis described in U.S. Pat. No. 6,751,563, which all contents thereof areincorporated by reference herein.

The techniques of the present disclosure can be used to automaticallymaintain program data and provide field wide updates upon which IEDfirmware and/or software can be upgraded. An event command can be issuedby a user, on a schedule or by digital communication that will triggerthe IED 100 to access a remote server and obtain the new program code.This will ensure that program data will also be maintained allowing theuser to be assured that all information is displayed identically on allunits.

It is to be understood that the present disclosure may be implemented invarious forms of hardware, software, firmware, special purposeprocessors, or a combination thereof. The IED 10 also includes anoperating system and micro instruction code. The various processes andfunctions described herein may either be part of the micro instructioncode or part of an application program (or a combination thereof) whichis executed via the operating system.

It is to be further understood that because some of the constituentsystem components and method steps depicted in the accompanying figuresmay be implemented in software, or firmware, the actual connectionsbetween the system components (or the process steps) may differdepending upon the manner in which the present disclosure is programmed.Given the teachings of the present disclosure provided herein, one ofordinary skill in the related art will be able to contemplate these andsimilar implementations or configurations of the present disclosure.

Furthermore, it is to be appreciated that the components and devices ofthe IED 10 of FIG. 1 may be disposed in various housings depending onthe application or environment. For example, the IED 100 may beconfigured as a panel meter 200 as shown in FIG. 2A an 2B. The panelmeter 200 of FIGS. 2A and 2B is described in more detail in commonlyowned U.S. Pat. No. 7,271,996, the contents of which are herebyincorporated by reference. As seen in FIGS. 2A and 2B, the IED 200includes a housing 202 defining a front surface 202 a, a rear surface202 b, a top surface 202 c, a bottom surface 202 d, a right side surface202 e, and a left side surface (not shown). Electrical device 200includes a face plate 204 operatively connected to front surface 202 aof housing 202. Face plate 204 includes displays 206, indicators 208(e.g., LEDs and the like), buttons 210, and the like providing a userwith an interface for visualization and operation of electrical device200. For example, as seen in FIG. 2A, face plate 204 of electricaldevice 200 includes analog and/or digital displays 206 capable ofproducing alphanumeric characters. Face plate 204 includes a pluralityof indicators 208 which, when illuminated, indicate to the user the“type of reading”, the “% of load bar”, the “parameter designation”which indicates the reading which is being displayed on displays 206, a“scale selector” (e.g., Kilo or Mega multiplier of Displayed Readings),etc. Face plate 204 includes a plurality of buttons 210 (e.g., a “menu”button, an “enter” button, a “down” button, a “right” button, etc.) forperforming a plurality of functions, including and not limited to:viewing of meter information; enter display modes; configuringparameters; performing re-sets; performing LED checks; changingsettings; viewing parameter values; scrolling parameter values; andviewing limit states. The housing 202 includes voltage connections orinputs 212 provided on rear surface 202 b thereof, and current inputs214 provided along right side surface 202 e thereof. The IED 200 mayinclude a first interface or communication port 216 for connection to amaster and/or slave device. Desirably, first communication port 216 issituated in rear surface 202 b of housing 202. IED 200 may also includea second interface or communication port 218 situated on face plate 204.

In other embodiment, the IED 100 may be configured as a socket meter220, also known as a S-base type meter or type S meter, as shown in FIG.2C an 2D. An exemplary socket meter is described in more detail incommonly owned U.S. Pat. No. 8,717,007, the contents of which are herebyincorporated by reference. Referring to FIGS. 2C and 2D, the meter 220includes a main housing 222 surrounded by a cover 224. The cover 224 ispreferably made of a clear material to expose a display 226 disposed onthe main body 222. An interface 228 to access the display and acommunication port 230 is also provided and accessible through the cover224. The meter 220 further includes a plurality of current terminals 232and voltage terminals 234 disposed on backside of the meter extendingthrough a base 235. The terminals 232, 234 are designed to mate withmatching jaws of a detachable meter-mounting device, such as a revenuemeter socket. The socket is hard wired to the electrical circuit and isnot meant to be removed. To install an S-base meter, the utility needonly plug in the meter into the socket. Once installed, a socket-sealingring 236 is used as a seal between the meter 220 and/or cover 224 andthe meter socket to prevent removal of the meter and to indicatetampering with the meter.

In a further embodiment, the IED 100 of FIG. 1 may be disposed in aswitchboard or draw-out type housing 240 as shown in FIGS. 2E and 2F,where FIG. 2E is a front view and FIG. 2F is a rear view. Theswitchboard enclosure 242 usually features a cover 244 with atransparent face 246 to allow the meter display 248 to be read and theuser interface 250 to be interacted with by the user. The cover 244 alsohas a sealing mechanism (not shown) to prevent unauthorized access tothe meter. A rear surface 252 of the switchboard enclosure 242 providesconnections for voltage and current inputs 254 and for variouscommunication interfaces 256. Although not shown, the meter disposed inthe switchboard enclosure 242 may be mounted on a draw-out chassis whichis removable from the switchboard enclosure 242. The draw-out chassisinterconnects the meter electronics with the electrical circuit. Thedraw-out chassis contains electrical connections which mate withmatching connectors 254, 256 disposed on the rear surface 252 of theenclosure 242 when the chassis is slid into place.

In yet another embodiment, the IED 100 of FIG. 1 may be disposed in anA-base or type A housing as shown in FIGS. 2G and 2H. A-base meters 260feature bottom connected terminals 262 on the bottom side of the meterhousing 264. These terminals 262 are typically screw terminals forreceiving the conductors of the electric circuit (not shown). A-basemeters 260 further include a meter cover 266, meter body 268, a display270 and input/output means 272. Further, the meter cover 266 includes aninput/output interface 274. The cover 266 encloses the meter electronics268 and the display 270. The cover 266 has a sealing mechanism (notshown) which prevents unauthorized tampering with the meter electronics.

It is to be appreciated that other housings and mounting schemes, e.g.,circuit breaker mounted, are contemplated to be within the scope of thepresent disclosure.

FIG. 3 illustrates an exemplary environment 300 in which the presentdisclosure may be practiced. The environment 300 includes at least oneIED 310 and at least one computing device 390, 391, 392. The network 302may be the Internet, a public or private intranet, an extranet, widearea network (WAN), local area network (LAN) or any other networkconfiguration to enable transfer of data and commands. An examplenetwork configuration uses the Transport Control Protocol/InternetProtocol (“TCP/IP”) network protocol suite, however, other InternetProtocol based networks are contemplated by the present disclosure.Communications may also include IP tunneling protocols such as thosethat allow virtual private networks coupling multiple intranets orextranets together via the Internet. The network 302 may supportexisting or envisioned application protocols, such as, for example,telnet, POPS, Mime, HTTP, HTTPS, PPP, TCP/IP, SMTP, proprietaryprotocols, or any other network protocols. During operation, the IED 310may communicate using the network 302 as will be hereinafter discussed.

It is to be appreciated that are at least two basic types of networks,based on the communication patterns between the machines: client/servernetworks and peer-to-peer networks. On a client/server network, everycomputer, device or IED has a distinct role: that of either a client ora server. A server is designed to share its resources among the clientcomputers on the network. A dedicated server computer often has fasterprocessors, more memory, and more storage space than a client because itmight have to service dozens or even hundreds of users at the same time.

High-performance servers typically use from two to eight processors (andthat's not counting multi-core CPUs), have many gigabytes of memoryinstalled, and have one or more server-optimized network interface cards(NICs), RAID (Redundant Array of Independent Drives) storage consistingof multiple drives, and redundant power supplies. Servers often run aspecial network OS—such as Windows Server, Linux, or UNIX—that isdesigned solely to facilitate the sharing of its resources. Theseresources can reside on a single server or on a group of servers. Whenmore than one server is used, each server can “specialize” in aparticular task (file server, print server, fax server, email server,and so on) or provide redundancy (duplicate servers) in case of serverfailure. For demanding computing tasks, several servers can act as asingle unit through the use of parallel processing. A client devicetypically communicates only with servers, not with other clients. Aclient system may be a standard PC that is running an OS such asWindows, Linux, etc.. Current OSes contain client software that enablesthe client computers to access the resources that servers share. OlderOSes, such as Windows 3.x and DOS, required add-on network clientsoftware to join a network. By contrast, on a peer-to-peer network,every computer or device is equal and can communicate with any othercomputer or device on the network to which it has been granted accessrights. Essentially, every computer or device on a peer-to-peer networkcan function as both a server and a client; any computer or device on apeer-to-peer network is considered a server if it shares a printer, afolder, a drive, or some other resource with the rest of the network.Note that the actual networking hardware (interface cards, cables, andso on) is the same in client/server versus peer-to-peer networks, it isonly the logical organization, management and control of the networkthat varies.

A client may comprise any computing device, such as a server 390,mainframe, workstation, personal computer 391, 392, hand held computer,laptop telephony device, network appliance, an IED 310, ProgrammableLogic Controller, Power Meter, Protective Relay etc. The client mayinclude system memory, which may be implemented in volatile and/ornon-volatile devices, and one or more client applications which mayexecute in the system memory. Such client applications may include, forexample, FTP client applications. File Transfer Protocol (FTP) is anapplication for transfer of files between computers attached toTransmission Control Protocol/Internet Protocol (TCP/IP) networks,including the Internet. FTP is a “client/server” application, such thata user runs a program on one computer system, the “client”, whichcommunicates with a program running on another computer system, the“server”. In one embodiment, IED 310 includes at least an FTP server.

While FTP file transfer comprises one embodiment for encapsulating filesto improve a data transfer rate from an IED to external clients, thepresent disclosure contemplates the use of other file transferprotocols, such as the Ethernet protocol such as HTTP or TCP/IP forexample. Of course, other Ethernet protocols are contemplated for use bythe present disclosure. For example, for the purpose of security andfirewall access, it may be preferable to utilize HTTP file encapsulationas opposed to sending the data via FTP. In other embodiments, data canbe attached as an email and sent via SMTP, for example. Such a system isdescribed in a co-owned U.S. Pat. No. 6,751,563, titled “ElectronicEnergy meter”, the contents of which are incorporated herein byreference. In the U.S. Pat. No. 6,751,563, at least one processor of theIED or meter is configured to collect the at least one parameter andgenerate data from the sampled at least one parameter, wherein the atleast one processor is configured to act as a server for the IED ormeter and is further configured for presenting the collected andgenerated data in the form of web pages, as will be described inrelation to FIG. 3.

IED 310 includes a digital sampler 320 for digitally sampling thevoltage and current of the power being supplied to a customer ormonitored at the point of the series connection in the power grid.Digital sampler 320 digitally samples the voltage and current andperforms substantially similar to the A/D converters 114 described abovein relation to FIG. 1. The digital samples are then forwarded toprocessor 330 for processing. It is to be appreciated that the processormay be a single processing unit or a processing assembly including atleast one CPU 150, DSP1 160, DSP2 170 and FPGA 180, or any combinationthereof. Also connected to processor 330 is external device interface340 for providing an interface for external devices 350 to connect tometer 310. These external devices might include other power meters,sub-station control circuitry, on/off switches, etc. Processor 330receives data packets from digital sampler 320 and external devices 350,and processes the data packets according to user defined or predefinedrequirements. A memory 360 is connected to processor 330 for storingdata packets and program algorithms, and to assist in processingfunctions of processor 330. These processing functions include the powerquality data and revenue calculations, as well as formatting data intodifferent protocols which will be described later in detail. Processor330 provides processed data to network 302 through network interface370, similar to the communication device 124 decribed above in relationto FIG. 1 In one embodiment, the network interface converts the data toan Ethernet TCP/IP format. The use of the Ethernet TCP/IP format allowsmultiple users to access the power meter simultaneously. In a likefashion, network interface 370 might be comprised of a modem, cableconnection, or other devices that provide formatting functions.

A web server program (web server) is contained in memory 360, andaccessed through network interface 370. The web server provides realtime data through any known web server interface format. For example,popular web server interface formats consist of HTML and XML formats.The actual format of the programming language used is not essential tothe present disclosure, in that any web server format can beincorporated herein. The web server provides a user friendly interfacefor the user to interact with the meter 310. The user can have variousaccess levels to enter limits for e-mail alarms. Additionally, the usercan be provided the data in a multiple of formats including raw data,bar graph, charts, etc. The currently used HTML or XML programminglanguages provide for easy programming and user-friendly userinterfaces.

The processor 330 formats the processed data into various networkprotocols and formats. The protocols and formats can, for example,consist of the web server HTML or XML formats, Modbus TCP, RS-485, FTPor e-mail. Dynamic Host Configuration Protocol (DHCP) can also be usedto assign IP addresses. The network formatted data is now available tousers at computers 390-392 through network 302, that connects to meter310 at the network interface 370. In one embodiment, network interface370 is an Ethernet interface that supports, for example, 100 base-T or10 base-T communications. This type of network interface can send andreceive data packets between WAN connections and/or LAN connections andthe meter 310. This type of network interface allows for situations, forexample, where the web server may be accessed by one user while anotheruser is communicating via the Modbus TCP, and a third user may bedownloading a stored data file via FTP. The ability to provide access tothe meter by multiple users, simultaneously, is a great advantage overthe prior art. This can allow for a utility company's customer servicepersonnel, a customer and maintenance personnel to simultaneously andinteractively monitor and diagnose possible problems with the powerservice.

FIG. 4 is a functional block diagram of processor 330 according to theembodiment of the present disclosure. Processor 330 is shown containingat least four main processing functions. The functions shown areillustrative and not meant to be inclusive of all possible functionsperformed by processor 330. Power Quality and Revenue Metering functions(metering functions) 410 consists of a complete set of functions whichare needed for power quality and revenue metering. Packet data collectedby digital sampler 320 is transmitted to processor 330. Processor 330calculates, for example, power reactive power, apparent power, and powerfactor. The metering function 410 responds to commands via the networkor other interfaces supported by the meter. External Device RoutingFunctions 430 handle the interfacing between the external device 350 andmeter 310. Raw data from external device 350 is fed into meter 310. Theexternal device 350 is assigned a particular address. If more than oneexternal device is connected to meter 310, each device will be assigneda unique particular address. The Network Protocol Functions 450 of meter310 are executed by processor 330 which executes multiple networkingtasks that are running concurrently. As shown in FIG. 4, these include,but are not limited to, the following network tasks included in networkprotocol functions 450: e-mail 460, web server 470, Modbus TCP 480, FTP490, and DHCP 492. The e-mail 460 network protocol function can beutilized to send e-mail messages via the network 302 to a user to, forexample, notify the user of an emergency situation or if the powerconsumption reaches a user-set or pre-set high level threshold. As theprocessor receives packets of data it identifies the network processingnecessary for the packet by the port number associated with the packet.The processor allocates the packet to a task as a function of the portnumber. Since each task is running independently the meter 310 canaccept different types of requests concurrently and process themtransparently from each other. For example, the web server may beaccessed by one user while another user is communicating via Modbus TCPand at the same time a third user may download a log file via FTP. TheNetwork to Meter Protocol Conversion Function 440 is used to format andprotocol convert the different network protocol messages to a commonformat understood by the other functional sections of meter 310. Afterthe basic network processing of the packet of data, any “commands” ordata which are to be passed to other functional sections of meter 310are formatted and protocol converted to a common format for processingby the Network to Meter Protocol Conversion Function 440. Similarly,commands or data coming from the meter for transfer over the network arepre-processed by this function into the proper format before being sentto the appropriate network task for transmission over the network. Inaddition, this function first protocol converts and then routes data andcommands between the meter and external devices.

Although the above described embodiments enable users outside of thenetwork the IED or meter is residing on to access the internal memory orserver of the IED or meter, IT departments commonly block this accessthrough a firewall to avoid access by dangerous threats into corporatenetworks. A firewall is a system designed to prevent unauthorized accessto or from a private network, e.g., an internal network of a building, acorporate network, etc.. Firewalls can be implemented in both hardwareand software, or a combination of both. Firewalls are frequently used toprevent unauthorized Internet users from accessing private networksconnected to the Internet, especially intranets. All messages enteringor leaving the intranet pass through the firewall, which examines eachmessage and blocks those that do not meet the specified securitycriteria. A firewall may employ one or more of the following techniquesto control the flow of traffic in and of the network it isprotecting: 1) packet filtering: looks at each packet entering orleaving the network and accepts or rejects it based on user-definedrules; 2) Application gateway: applies security mechanisms to specificapplications, such as FTP and Telnet servers; 3) Circuit-level gateway:applies security mechanisms when a TCP or UDP connection is established,once the connection has been made, packets can flow between the hostswithout further checking; 4) Proxy server: intercepts all messagesentering and leaving the network, effectively hides the true networkaddresses; and 5) Stateful inspection: doesn't examine the contents ofeach packet but instead compares certain key parts of the packet to adatabase of trusted information, if the comparison yields a reasonablematch, the information is allowed through, otherwise it is discarded.Other techniques and to be developed techniques are contemplated to bewithin the scope of the present disclosure.

In one embodiment, the present disclosure provides for overcoming theproblem of not being allowed firewall access to an IED or meterinstalled within a facility, i.e., the meter is residing on a privatenetwork, by enabling an IED to initiate one way communication throughthe firewall. In this embodiment, the IED or meter posts the monitoredand generated data on an Internet site external to the corporate orprivate network, i.e., on the other side of a firewall. The benefit isthat any user would be able to view the data on any computer or webenabled smart device without having to pierce or bypass the firewall.Additionally, there is a business opportunity to host this data on a webserver and charge a user a monthly fee for hosting the data. Thefeatures of this embodiment can be incorporated into any telemetryapplication including vending, energy metering, telephone systems,medical devices and any application that requires remotely collectingdata and posting it on to a public Internet web site.

In one embodiment, the IED or metering device will communicate throughthe firewall using a protocol such as HTTP via a port that is openthrough the firewall. Referring to FIG. 5, IEDs or meters 510, 512, 514reside on an internal network 516, e.g., an intranet, private network,corporate network, etc. The internal network 516 is coupled to anexternal network 522, e.g., the Internet, via a router 520 or similardevice over any known hardwire or wireless connection 521.

A firewall 518 is disposed between the internal network 516 and externalnetwork 522 to prevent unauthorized access from outside the internalnetwork 516 to the IEDs or meters 510, 512, 514. Although the firewall518 is shown between the internal network 516 and the router 520 it isto be appreciated that other configurations are possible, for example,the firewall 518 being disposed between the router 520 and externalnetwork 522. In other embodiments, the firewall 518 and router 520 maybe configured as a single device. It is further to be appreciated thatfirewall 518 can be implemented in both hardware and software, or acombination of both.

The communication device or network interface of the meter (as describedabove in relation to FIGS. 1 and 4) may communicate through the firewall518 and read a web site server 524. It is to be appreciated that the oneway communication from the IED through the firewall may be enabled byvarious techniques, for example, by enabling outbound traffic to the IPaddress or domain name of the server 524 or by using a protocol that hasbeen configured, via the firewall settings, to pass through the firewallsuch as HTTP (Hyper Text Transfer Protocol), IP (Internet Protocol), TCP(Transmission Control Protocol), FTP (File Transfer Protocol), UDP (UserDatagram Protocol), ICMP (Internet Control Message Protocol), SMTP(Simple Mail Transport Protocol), SNMP (Simple Network ManagementProtocol), Telnet, etc. Alternatively, the IED may have exclusive accessto a particular port on the firewall, which is unknown to other users oneither the internal or external network. Other methods or techniques arecontemplated, for example, e-mail, HTTP tunneling, SNTP trap, MSN,messenger, IRQ, Twitter™, Bulletin Board System (BBS), forums, UniversalPlug and Play (UPnP), User Datagram Protocol (UDP) broadcast, UDPunicast, Virtual Private Networks (VPN), etc.

The server 524 will provide instructions in computer and/or humanreadable format to the IED or meter. For instance, the web server 524might have XML tags that state in computer readable format to providedata for the last hour on energy consumption by 15 minute intervals. Themeter 510, 512, 514 will then read those instructions on that web server524 and then post that data up on the server 524. In this manner, theIED or meter initiates communication in one direction, e.g., an outbounddirection, to the server 524.

Another server (or can be in one server) will read the data that themeter 510, 512, 514 posts and will format the meter data into data thatcan be viewed for humans on a web site or a software application, i.e.,UI Server 526. Servers 524, 526 can also store the data in a database orperform or execute various control commands on the data. Clients 528 mayaccess the IED data stored or posted on servers 524, 526 via aconnection to the network 522.

Since the meters are only communicating in an outbound direction only,the meters 510, 512, 514 can read data or instructions from an externalnetwork application (e.g., server 524), the external network applicationcannot request information directly from the meter. The server 524 poststhe data or instructions on the web site and waits for the meter tocheck the site to see if there has been a new post, i.e., newinstructions for the meter. The meter can be programmed at the user'sdiscretion as to frequency for which the meter 510, 512, 514 exits outto the external network to view the postings.

The meter instruction server 524 will post instructions in a directoryprogrammed/located on the server or into XML or in any fashion that themeter is configured to understand and then the meter will post whateverdata it is instructed to do. The meter can also be configured toaccomplish control commands. In addition to the meter instruction server524, a user interface (UI) server 526 is provided that can be used toenable a user interface to the user. The user can provide input on theUI server 526 that might trigger the meter instruction server 524 toproduce a message to control the energy next time the meter reads thatserver.

In another embodiment, the TED or metering device will communicatethrough the firewall using a server (not shown) disposed on an internalnetwork protected by a firewall. In this embodiment, the serveraggregates data from the various IEDs 510, 512, 514 coupled to theinternal or private network 516. Since the server and the IEDs 510, 512,514 are all on the same side of the firewall 518, generallycommunications and data transfers among the server and the IEDs 510,512, 514 is unrestricted. The server then communicates or transfers thedata from the IEDs to server 524 on the external network on the otherside of the firewall 518. The communication between server on theinternal network and server 524 may be accomplished by any one of thecommunication means or protocols described in the present disclosure.The server 524 then posts the data from the IEDs 510, 512, 514 makingthe data accessible to clients 528 on external networks, as describedabove.

In a further embodiment, the server disposed on the internal networkcommunicates or transfers the data from the IEDs to clients 528 on theexternal network on the other side of the firewall 518, without the needto transfer or pass data to a server on the external network.

In another embodiment, each IED 510, 512, 514 may be configured to actas a server to perform the functionality described above obviating theneed for a separate server.

Furthermore, in another embodiment, each IED 510, 512, 514 and eachclient device 528 may be configured as a server to create a peer-to-peernetwork, token ring or a combination of any such topology.

The systems and methods of the present disclosure may utilize one ormore protocols and/or communication techniques including, but notlimited to, e-mail, File Transfer Protocol (FTP), HTTP tunneling, SNTPtrap, MSN, messenger, IRQ, Twitter™, Bulletin Board System (BBS),forums, Universal Plug and Play (UPnP), User Datagram Protocol (UDP)broadcast, UDP unicast, Virtual Private Networks (VPN), etc. Common chatprotocols, such as MSN, AIM, IRQ, IRC, and Skype, could be used to senda message, containing the meter's data, to a public chat server whichcould then route that message to any desired client. A public socialserver that supports a common web interface for posting information,such as Twitter™, Facebook™, BBS's, could be used to post a status,containing the meter's data, to a user on the public social server forthat service, e.g., server 440, 540, 640. This post could then be viewedby the clients to see the meter's data, or read by another server forfurther parsing and presentation. Hosted data services, such as a hosteddatabase, cloud data storage, Drop-Box, or web service hosting, could beused as an external server to store the meter's data, called Hosting.Each of these Hosts, e.g., server 540, could then be accessed by theclients to query the Hosted Data.

In another embodiment, the IEDs can communicate to devices using GenericObject Oriented Substation Event (GOOSE) messages, as defined by theIEC-61850 standard, the content of which are herein incorporated byreference. A GOOSE message is a user-defined set of data that is“published” on detection of a change in any of the contained data itemssensed or calculated by the IED. Any IED or device on the LAN or networkthat is interested in the published data can “subscribe” to thepublisher's GOOSE message and subsequently use any of the data items inthe message as desired. As such, GOOSE is known as a Publish-Subscribemessage. With binary values, change detect is a False-to-True orTrue-to-False transition. With analog measurements, IEC61850 defines a“deadband” whereby if the analog value changes greater than the deadbandvalue, a GOOSE message with the changed analog value is sent. Insituation where changes of state are infrequent, a “keep alive” messageis periodically sent by the publisher to detect a potential failure. Inthe keepalive message, there is a data item that indicates “The NEXTGOOSE will be sent in XX Seconds” (where XX is a userdefinable time). Ifthe subscriber fails to receive a message in the specified time frame,it can set an alarm to indicate either a failure of the publisher or thecommunication network.

The GOOSE message obtains high-performance by creating a mapping of thetransmitted information directly onto an Ethernet data frame. There isno Internet Protocol (IP) address and no Transmission Control Protocol(TCP). For delivery of the GOOSE message, an Ethernet address known as aMulticast address is used. A Multicast address is normally delivered toall devices on a Local Area Network (LAN). Many times, the message isonly meant for a few devices and doesn't need to be delivered to alldevices on the LAN. To minimize Ethernet traffic, the concept of a“Virtual” LAN or VLAN is employed. To meet the reliability criteria ofthe IEC-61850, the GOOSE protocol automatically repeats messages severaltimes without being asked. As such, if the first GOOSE message gets lost(corrupted), there is a very high probability that the next message orthe next or the next will be properly received.

The above-described devices, systems and methods enable a cloud-basedmeter management system, which will be described in greater detailbelow.

Referring to FIG. 6. the system 600 of the present disclosure includes ameter cloud server 602, a plurality of IEDs or meters 604 and 606, andone or more clients 608 (e.g., a web browser client), which are coupledtogether via a network 610 (e.g., via various wireless and/or hardwiredcommunication networks). The various components and modules of thesystem of the present disclosure provide a plurality of functions toenable one or more users to manage a plurality of IEDs or meters via atleast one client device 608.

The meter cloud system 600, at its most basic, stores meter log data 612in the cloud, i.e., a meter cloud server 602, so that it is accessibleby a web client 608. To achieve this, meter log data 612 is uploaded tothe meter cloud server 602 directly by a Meter Cloud Enabled Meter 606,or by a Meter Manager module or software 614 executing on a processor ofa computing device (e.g., a server, as will be described below) usinglog data retrieved from a meter 604. The Meter Cloud Server 602 thenstores that data and provides the data to a user with a web browserclient 608 when requested.

The techniques of the present disclosure enable the following features:upload meter log data 612 to the Meter Cloud Server 602 using a JSON logdata format (or any other suitable format); preform Registration andUnregistration of meters 604, 606, associating meters 604, 606 with thecorrect customer in the process, simplifying the registration processfor the user; provide list to easily identify which meters 604, 606 havebeen registered to the cloud server 602; and provides direct links to aselected meter in the web browser client 608.

The meter cloud system 600 links meters such as meters 604, 606, logdata 612, meter manager module 614, and cloud server 602 into onecohesive mesh, allowing varying levels of data to be accessible from anyclient 608 coupled to network 610. In one embodiment, a common WebAPIprotocol links each of the components, allowing simple interchange ofdata. In other embodiments, the components are linked using multipleprotocols.

Components of the meter cloud system 600 will now be described in moredetail below.

Meter Cloud Server 602: The meter cloud server 602 provides storage andretrieval for the Meter Log Data 612, management of Users and Customers,as well as additional meta actions, such as, but not limited to, thegeneration of reports on the data received from meters 604, 606(including log data 612). The Meter Cloud Server 602 of the presentdisclosure provides the following features: provides a Web Service forlog data uploads, retrievals, security logins, and meter management;stores meter log data 612 for later retrieval by clients 608; providesuser security, such that meters 604, 606 are associated with customers,and only users which have permission for that customer can view the dataassociated to meter or meters 604, 606; serves web resources that aredisplayed and can be viewed on web browser client 608; and Single Cloudsoftware, running on the cloud server 602. Cloud server 602 collectsmeter information and a reduced subset of log data, stores them in adatabase or other storage medium, and provides a single website and webservices that a web client, e.g., 608, can execute and use to query anddisplay the meter data for their location. Meters 604, 606 are organizedby customer and location, and log data is pushed up to the cloud server602 (via web services) by the meter manager module 614 (which providesdata from meters 604) and web service enabled meters 606.

Meter Manger Module 614: Meter Manager Module 614 plays two roles in theMeter Cloud system 600. First, it collects meter log data 612 fromnon-web service enabled meters 604, and pushes the compatible data up tothe Cloud server 602. Secondly, it provides full access to the data ofmeters 604 via its own set of web services, using the same protocols asthe Cloud server 602. The web services including registration, upload,and query. To enable this, the Meter Manager Module 614 employs a WebAPIRPC control structure, extended to provide a WebAPI Log Service to logdata, as well as including cloud configuration and management tools.

Meter 604: For non-web service enabled meters 604, the meter managermodule 614 will perform log collection and upload to the Cloud server602.

Meter Cloud Enabled Meter 606: Certain meters of the present disclosureare configured to register and upload their own logs to the meter cloudserver 602 using a JSON log data format, on an interval, i.e., areconfigured to push data up to the Cloud server 602 directly (e.g., usingat least one processor and at least one communication module), using thesame protocol as the meter manager module 614. The meters 606 mayperform this automatically, following an initial commissioning phase,that enables the meter for integration with the cloud server 602.

Web Browser Client 608: A web browser client 608 executes and displaysthe main Meter Cloud User Interface (UI) for managing meters, users, andviewing meter data. The UI is presented as a web page, viewed through aweb browser, such as Chrome, Firefox, Edge, Safari, iPhone, Android,etc., that is executed by a processor of the client 608. The web browserclient 608 is configured to provide the following features via theexecution and display of the Meter Cloud UI: responsive layout, allowingfor both small layout browsers such as a phone, and large layoutbrowsers; organizes meters 604, 606 by facility; provides a login pageto prevent unauthorized access; provides a create new user option, wherethe user can create a new customer, or associate themselves with anexisting one; provides user management interfaces for admin users, toassign access rights to individual users within a customer; and providesindividual meter dashboards for viewing a meter's log data.

Protocol: In one embodiment, all interactions with the meter cloudserver 602, including uploading data, configuring meters, and queryingmeter data, use a single Web API protocol, using JSON for its format.The present disclosure provides a common protocol between all componentsin the meter cloud system 600. The Web API uses a REST (representationalstate transfer) style interface, and a JSON body format and providesinterfaces for: Uploading Data; Downloading Data; Querying LogInformation; and Configuring Meters. In another embodiment, theinteractions with meter cloud server 602 may use multiple differentprotocols specific to a given task or function performed betweencomponents of system 600.

Referring to the FIG. 7, in one embodiment, the meter cloud system 600includes at least the following components: a cloud server 602, a widearea network (WAN) 704 and a local area network (LAN) 706, which will bedescribed in more detail below.

-   -   Cloud Server 602: Hosted on a cloud web service provider, the        cloud server 602 provides access to meters 604, 606 and data for        clients 608 outside of the private LAN 706 of a customer. A        single server (or cluster) provides access to the data of        multiple customers, using security and API keys to segregate the        data of one customer from another. Usage of the cloud server 602        may be a billed service, including upload of data, management of        meters 604, 606, and retrieval of meter data. The cloud server        602 includes three of the following components:        -   Web Server 650—Provides access to the web resources and UI,            such as images and web pages, used by the WAN web clients            608. Uses the Web Services to provide dynamic data content            to clients 608.        -   Web Services 652, 654—Provides data access and manipulation            services for meters 604, 606, logs 612, security, users, and            registration. Provides a common protocol that can be used by            meters 606, the meter manager module 614, web clients 608,            and third party applications to upload and retrieve log data            612.        -   Database 656—Stores meter, location, customer, user, and log            configuration and data, to be used and manipulated by the            Web Services.        -   Database Controller 658 is configured to enable access to            database 656.    -   WAN 704: Web Clients 608 operating on the Internet 610 connect        to the Cloud server 602 to configure and view meter data, using        a customer's user information and API key.    -   LAN 706: Local Area Network

Interior to a customer's private network, i.e., LAN 706, reside themeters 604, 606 and servers 702 which collect log data 612, and providedirect access to that data 612. The meter manager module 614 collectsdata from all the meters, stores full detail logs internally (e.g., inat least one memory), and uploads a reduced subset (e.g., having apredetermined and/or user-configured subset of the data stored on eachmeter 604, 606 that meter manager 614 determines (e.g., viauser-configured preferences) is most important/useful for the user) tothe cloud server 602 for consumption by Web Clients 608 on WAN 704.Additionally, it provides Web Service access to clients 708 interior tothe LAN 706 using the same protocol as that used on Cloud server 602,allowing for richer clients with access to the full set of data. Asshown in FIG. 8, the LAN 706 includes at least a server 702, meters 604,web meters 606 and client PCs 708.

-   -   Server 702: The Server 702 is the center of the LAN system,        meter manager 614 runs on server 702 to provide all data        collection, query, and push services.    -   Meter data collected is stored locally to the server 702 in        either old MS Access databases (or other legacy databases), or        in a Massive Table format PostGreSQL databases (or other type of        modern database format).    -   The Meter Manager Server 702 provides (in some embodiments) the        same web services as the Cloud server 602, allowing web service        enabled meters to register with, and upload data directly to        Meter Manager server 602.    -   Additionally, clients 608 can use the same query protocols to        read meter data directly from the Cloud server 602 or from Meter        Manager server 602.    -   Meters 604: Meter log data 614 is collected via log retrieval by        Meter Manager server 702, and stored on the server to be used by        LAN clients 708 and pushed up to the Cloud server 602.    -   Web Meters 606: For meters which are web service enabled, they        can directly register and push data up to the Cloud server 602.        However, if a firewall requires individual configuration to        allow outbound web requests, the web meter 606 can be configured        to register and push to the Meter Manager Server 702, which can        then provide the upload service.    -   Client PC 708: Client PC's 708 on the LAN 706 can access meter        log data and configuration through Meter Manager Web Services.

The Meter Cloud System of the present disclosure enables at least, butnot limited to, the following features:

-   -   Common WebAPI protocol for configuration, registration, data        upload and query, and login.    -   Customer API key will be used to provide restricted user API        access.    -   Cloud Service via cloud server 602, which provides access to a        restricted log data set from the Internet.    -   Upload Service provided by Meter Manager 614 to push log data        612 up to the Cloud Sever 602.    -   Customer segregation in the Cloud Service, such that one        customer cannot access the data of another.    -   Security management and login in both the Cloud Service, and the        Meter Manager Service provided by Meter Manager 614, allowing        only verified users to access and configure the servers 602,        702.    -   Web Service Enabled Meters 606 are configured to register and        upload data directly to the cloud server 602.    -   Meter Manager Server 702 (including meter manager 614) is        configured to provide all the Web Service functionality of the        cloud server 602, allowing clients to upload and query the same.    -   Meter Manager Server 702 will provide storage and access to the        full data in the stored meter log databases 660A, 660B that are        accessible by meter manager 614 and server 702 (e.g., meter log        databases stored in server 702). It is to be appreciated that        log data in meter databases 670 stored in client device 708 may        be synced to meter log databases 660, such that, meter manager        614 may upload log data received from meter database 670 to        cloud 602.    -   A Massive Table PostGreSQL database will be available in server        702 to store meter log data in one centralized location.    -   Meter Manager Server 702 is configured to retrieve and store log        data 612 for meters 604, 606 interior to the customers network,        e.g., LAN 706.    -   Meter Manager Server 702 is configured to extend access via web        queries to allow other softwares to access the services from        other PCs in the LAN 706.    -   Meters 604, 606 may be organized into Locations in the Cloud        server 602, and tied to location information configured by the        Customer.

It is to be appreciated that system 600 employs a network configurationthat enabled load balanced data and communication flow in accordancewith an embodiment of the present disclosure. For example, referring toFIG. 9, a network configuration of the server 602 is shown in accordancewith an embodiment of the present disclosure. It is to be appreciatedthat server 602 may be configured from several physical or virtualservers or one physical or virtual server including the functionality ofthe individual components shown in FIG. 9. The network configurationincludes a DNS and certificate service 804, which connects a user 802 tothe application executing in cloud server 602. The network configurationemploys load balancing (e.g., elastic load balancing), via loadbalancers 812, 814, 816. Load balancers 812, 814, 816 automaticallydistribute incoming application traffic to server 602 to multipledestinations or routes to efficiently manage large amounts of incomingapplication traffic. The load balancers 812, 814, 816 may furtherincorporate custom rules for routing incoming application traffic (e.g.,forcing https (SSL), etc.). It is to be appreciated that there are 3different webservices, a push service 820, billing service 822, and aquery service 818, each of which will be described below. Each of these3 services speaks to it's own load balancer. If the push Service iscalled, then it speaks to the pushLoadBalancer 814, if the BillingService 822 is called, it speaks to the BillingLoadBalancer 816 and, ifthe query Service 818 is called, it speaks to the queryLoadBalancer 812.

The network configuration further includes a web application firewall(WAF) 810 (described in greater detail below), logs 808 (including logdata from WAF 810 and balancers 112/114/116), and storage 106 (e.g., oneor more storage devices or facilities for storing logs 108 and databackups from data in server 602). All requests to any of the services,e.g., service 818, 820, 882, always go through the web applicationfirewall (WAF) 810 first and will be blocked if the firewall has anissue with the incoming request.

The network configuration supports services 818, 820, 822, e.g., RESTservices. The query service 818 runs throughout the whole cloudmanagement application and also allows application calls to otherapplications internal to server(s) 602, e.g., requests for data and/orlogs. The push service 820 is a webservice that receives meter log datafrom various sources, such as, an application installed on the LAN 706(e.g., meter manager module 614 on server 702). Push service 820 is usedto upload log date from meters 604, 606 to server(s) 602. The billingservice 822 is a billing and management web service of server(s) 602that is configured to handle any billing or managements issues/mattersusers may have. It is to be appreciated that services 818, 820, 822 areinstalled on one or more servers 602 configured for autoscaling suchthat if the load (e.g., data pushed to server, queries or polling of theserver, etc.) on one of the servers 602 is above a predetermined limit,the network and/or server 602 is configured to employ at least oneadditional server to accommodate for the increased load (alternatively,the network and/or server 602 further decreases the amount of servers inuse when the load on the servers 602 is decreased). In one embodiment,the applications in the network configuration (e.g., such as services818, 820, 822) are deployed on ElasticBeanStalk (i.e., a service fordeploying and scaling web applications and services) and Docker (i.e.,an open source tool for deploying applications).

It is to be appreciated that although only three (3) services are shown,e.g., services 818, 820, 822, it is contemplated that more than threeservices may be employed in system 600. As additional services areemployed, additional corresponding load balancers may also be employed.

The network configuration of FIG. 9 further includes another loadbalancer 824 (e.g., an elastic load balancer), which supports TCP forcommunication with a database (e.g., MySQL) 832 for storing relationaland structured data, such as, but not limited to, facility information,user information, and meter information.

The network configuration further includes a database 826 (e.g.,non-relational database) configured for time series data. Database 826stores logs from meters 604, 606 in an unstructured format. Database 826stores History, PQ, Limit, Wave, and System Event Logs from meters 604,606.

The network configuration further includes a databus or message broker828, e.g., RabbitMQ™, for routing communications in multiple differentprotocols between components of the network configuration of FIG. 9.Databus 828 is configured to handle call load to the various databasesof cloud 602 such that instead of every call being directly sent to agiven database of cloud server(s) 602, a call is made to databus 828 anddatabus 828 is configured to then route the call to the appropriatedatabase. Databus 828 is configured to enable async calls and includes aPublish/Subscribe tool where a service publishes to databus 828 and thenan object/entity/service may subscribe to get the data (e.g., aconsumer) and send the data back to databus 828, which sends the data tothe original caller service.

The network configuration further includes a log server 830, which logsall calls made by the webservice and store the calls in logs in server830. The network configuration also includes consumers 834, 836, 838,840. Consumer 834 communicates with databus 828 and collects all of thecalls from query service 818 and send the calls to database 826 andreturns data from the database 826. Push consumer 836 interfaces withthe push server 820 and captures push data sent to databus 828 andstores the push data in database 826. Metadata consumer 838 isconfigured to enables anyone in the network to communication withdatabase 832 without any knowledge about where data is stored. Metadataconsumer 838 wraps all of the interactions of database 832 (and makescalls to database 826) for the website generated by server 602 andpresented to client device 608. Metadata consumer 838 receives requestsfrom databus 828, sends the requests to the appropriate database, andpushes responses to the requests from the databases to databus 828.Python consumer 840 is configured to get all of the data from the meterlogs as well as weather data from a third party weather API and buildout prediction models (e.g., billing predictions) that are used.

In one embodiment, database 832 is a relational database and stores datain Tables and Rows. Database 832 is used in the system for ‘structureddata’ like facility information, user login/pass, customer information(first/last name, address etc.). Database 826 is a NoDB system (i.e., isknown as a Time Series NoDB which is a NoDB focused on time data whichis all the meter logs). A NoDB stores unstructured data which can changeeasily and stores it in a JSON style format. It is not as rigid as arelational database and allows for data to be stored better in the caseof logs and things that are not structured. As an example, one wave filecan contain 100 pieces of data, while another can contain 34, another275 etc.

Referring to FIG. 10, a user login flow diagram is shown in accordancewith an embodiment of the present disclosure. A user logs into thesystem 1002 (e.g., via a UI displayed in a web browser of client device608), a database of server 602 takes the login information and validatesit 1004 (e.g., by checking information 1005 including customer IDinformation, such as, but not limited to, API keys and customer rolesamong other information) in the database system (in one embodiment,BCrypt is employed to encrypt passwords in the database). If invalid1006, cloud server 602 returns invalid to the user (and displays theresult in the UI displayed in the web browser). If valid 1006, cloudserver 602 logs the user into the system and gets 1010 the information1005 for the user such as basic information, e.g., their APIKey, whichcloud server 602 can use to associate the meters 604, 606 to and theirrole as an Enterprise User or a Simple user (or other type of user) ofthe system 600 as well as the EIGlog will capture a login of this userinto the system.

Referring to FIG. 11, a meter registration flow diagram is shown inaccordance with an embodiment of the present disclosure. In step 1102,when an attempt is made to register a meter 604, 606, a register meterAPI command is sent to server 602. In step 1104, server 602 queries ameter list including all registered meters 604, 606, if the meter 604,606 is already registered, in step 1106, server 602 sends a notification(e.g., to a user on a client device 608) that the meter is alreadyregistered. The notification may include information (e.g., meter ID,meter type, etc.) associated with the registered meter. Alternatively,if, in step 1104, server 602 finds that the meter 604, 606 has not beenregistered, in step 1108, information associated with the new meter 604,606 (e.g., meter ID, meter type, meter settings (e.g., CT/PT ratio,energy scaling, hookup info, etc.)) is registered, and in step 1110, thenew meter 604, 606 is registered (e.g., in a database including a meterlist). In step 1112, a server database of server 602 is initialized andthe information associated with the new meter 604, 606 is stored. Instep 1116, the meter settings information associated with the new meter604, 606 is used to update the meter settings stored in the serverdatabase.

User registration is done through a webpage provided by the cloud server602 to a client 608. When a user registers with the cloud server 602(e.g., via a UI displayed in a web browser of client device 608), theyare given the option of creating a new customer, or joining in anexisting customer's group of users. If the user creates a new customer,a unique APIKey is generated, to be used by all users of this Customer.Alternatively, when a user registers, they can join an existingcustomer's group of users, thus accessing that customers meters 604,606. To join an existing customer's group, the user must acquire andenter that customer's APIKey (generated above, and provided by the userthat created the customer to the user desiring to join the group), toverify (by server 602 checking a database including the customerinformation) they have legitimate access to this customer. Whether theuser creates a customer, or joins an existing one, that APIKey isassociated with that user account. This APIkey is then used by the meterdata push service of server 602 to verify that the upload has legitaccess to the meter data being modified.

Referring to FIG. 12, an overview of the interaction between a user andcloud server 602 is shown in accordance with the present disclosure.Since the client software or website being accessed by client browserneeds the CustKey to perform any action, the user must login before thesoftware can interact with the cloud server 602. After creating a user,or just logging in, the cloud server 602 will query the CustKey for thelogged in user, and store this for usage by uploads and meterregistration, as shown above in the overview of client softwareinteraction.

The interaction between client devices 608, meter manager module 614,and/or web-enabled meters 606 with the components of cloud server 602shown in the network configuration of FIG. 9 will now be described inrelation to FIGS. 32-34.

Referring to FIG. 32, a flow diagram illustrating a method for pushingdata (e.g., log data) to cloud server 602 and how server 602 handles thepushed data is shown in accordance with an embodiment of the presentdisclosure. In step 3202, meter manager module 614 or a web-enabledmeter 606 uses an HTTP POST method to provide data to push service 820of server 602. In step 3204, push service 820 pushes the data to databus826, and in step 3206, databus 826 pushes the data to push consumer 836.In step 3208, push consumer 836 pushes the data to database 826. In step2310, consumer 836 pushes historical channel data (e.g., associated witha predetermined time period, such as a day) to databus 826, and, in step3212, databus 826 provides the historical data to consumer 834. In step3214, query consumer 834 requests all the historical data for theupdated period (e.g., meter data or channel data associated with apredetermined period of time, such as a day) from database 826. In step3216, database 826 responds to the request by providing the channel datarequested to query consumer 834. In step 3218, the query consumer 834stores the sum/avg data for this channel for the specified day indatabase 826.

Referring to FIG. 33, a flow diagram illustrating a method for handling(e.g., pushing) various types of data (e.g., power quality, waveform,limit, and event data) is shown in accordance with an embodiment of thepresent disclosure. In step 3202, meter manager module 614 or aweb-enabled meter 606 uses an HTTP POST method to provide data (e.g.,log data) to push server 820 of server 602. In step 3304, service 820pushes the data to databus 826. In step 3306, databus 826 sends the datato consumer 836, which pushes the data to database 826, in step 3308.

Referring to FIG. 34, a flow diagram illustrating a method for using thenetwork configuration of FIG. 9 in system 600 is shown in accordancewith an embodiment of the present disclosure. In step 3402, cloud UI3401 e.g., a website and/or UI, the code for which is stored on server602 and executed by a client browser to be displayed on a display ofclient 608, uses an HTTP POST method provided to query service 834 tolog in to the website/database cloud system hosted on server 602. It isto be appreciated that any of the UIs disclosed herein may berepresented by cloud UI 3401. In step 3404, service 834 pushesauthentication data received in the POST method to databus 828, whichsends the authentication data to metadata consumer 838, in step 3406. Instep 3408, metadata consumer 838 sends a request to database 832 tocheck to the authentication data against authentication stored indatabase 832 (e.g., against a user name and password of the user), and,in step 3410, database 832 responds to the request with user data if thecheck was successful and sends the user data to consumer 3410.

In step 3412, consumer 838 sends the user data to databus 828, whichsends the data to service 834, in step 3414. In step 3416, service 834generates a token based on the user data, and, in step 3418, service 834provides or returns to the token to the cloud UI.

In step 3420, the cloud UI uses an HTTP GET method to get the currentuser details (e.g., name, user ID, email address, associated clientinformation such as an APIKEY, etc.) from service 834. Responsive to theGET method, service 834 responds with the user data requested andprovides the user data to the cloud UI, in step 3422. In step 3424, thecloud UI sends an HTTP GET method to service 834 to request facilitydata (e.g., facility name, facility ID, facility address and otherfacility information) associated with meters 604, 606 in a user's fleet.In step 3426, service 834 pushes the request to databus 828, and, instep 3428, databus 828 sends to the request to consumer 838. In step3430, consumer 838 sends a request to database 832 to determine (e.g.,based on the API key and user ID associating users with particularfacilities and meters) the facility associated to the user making therequest. In step 3432, database 832 responds to the request by providingthe facility data to consumer 838. In step 3434, based on the facilitydata, consumer 838 sends a request for data (e.g., a listing of themeters) associated with the meters 604, 606 at the facility determinedto database 832, and, in step 3436, database returns the meter datarequested to consumer 838 responsive to the request. In step 3438,consumer 838 sends a facility list with the meters 604, 606 at theparticular facility (and/or all facilities for that user with theirassociated meters) to databus 828, and, in step 3440, databus 828 sendsthe facility list with the meters 604, 606 to service 834, whichprovides the list to the cloud UI, in step 3442.

In step 3444, cloud UI sends an HTTP GET method to service 834 torequest data or statistics associated with meters 604, 606. In someembodiments the data is requested in a series of asynchronous calls. Instep 3446, the request is pushed by service 834 to databus 828, and, instep 3448, databus 828 sends the request to consumer 834. In step 3450,responsive to the request consumer 834 sends a request to database 826to get a count of events associated with the data or statics requestedin step 3444. In step 3452, database 826 responds to the request andsends the count of the events to consumer 834. In step 3454, consumersends the meter data or statistics requested in step 3444 to databus828, databus 828 sends the meter data or statistics to service 834, instep 3456, and service 834 sends the meter data or statistics to thecloud UI, in step 3458.

In step 3460, the cloud UI sends an HTTP GET method to services 834 torequest meter channel data (e.g., current, voltage, or other datameasured and calculated by each meter 604, 606) relating to the metersin the list returned in step 3442. In step 3462, the request is pushedby consumer 834 to databus 828. In step 3464, databus 828 sends therequest to consumer 834. In step 3466, consumer 834 sends a request forthe channel data to database 826, and, in step 3468, database 826returns the channel data to consumer 834. In step 3470, the channel datais provided by consumer 834 to databus 828. In step 3472, the channeldata is provided by databus 828 to service 834. In step 3474, thechannel data is provided by service 834 to the cloud UI.

It is to be appreciated that the sequence of steps 3444, 3446, 3448,3450, 3452, 3454, 3456, 3458 may be performed several times insuccession. Furthermore, it is to be appreciated that steps 3460, 3462,3464, 3466, 3468, 3470, 3472, 3474 may be performed in parallel withsteps 3444, 3446, 3448, 3450, 3452, 3454, 3456, 3458.

Referring to FIG. 13, a block diagram of the meter manager module 614 ofthe cloud meter system 600 in accordance with the present disclosure isprovided.

-   -   WebAPI Hosts—Host classes are used to listen to WebAPI requests        for both RPC and Log API's.    -   WebAPI RPC Server 750—The RPCServer class supports WebAPI        requests, from either a RPCClient, or directly from a Web Client        608/708.    -   Log Service 752—Internal service which manages the meter log        databases stored by meter manager module 614, and provides the        WebAPI Host for Logs.    -   LogDb Massive 754—Database Server based meter log data storage.    -   LogUtils LogDb_Massive—LogUtils DataSource interface to read        LogEventLists from the LogDb Massive. This allows all existing C        # applications to be easily migrated to the new database.    -   LogUtils LogDb_Cloud 764—LogUtils DataSource interface to read        meter log data from the Cloud WebAPI. This allows all existing C        # applications to be easily migrated to the new datastorage.    -   Security 756—Security Manager which will ensure that only        authorized users can access meter manager resources through the        various WebAPI interfaces.    -   CloudDb 758—Storage of information related to interfacing with        the cloud server 602, including Customer Login information and        meter upload configurations.    -   Cloud Upload Service 760—Service which monitors the retrieval of        logs from meters, and uploads new data to the cloud server 602.    -   Cloud Register Service 762—Service which registers and        configures meters in the cloud server 602 for the user.

Referring to FIG. 14, the Log Service performed by meter manager module614 is shown in greater detail in accordance with the presentdisclosure.

Referring to FIG. 15, the cloud upload service of meter manager module614 is shown in accordance with of the present disclosure. Referring toFIG. 16, the WebAPI RPC 750 feature of system 600 is shown in accordancewith of the present disclosure.

Referring to FIG. 17 a block diagram of a meter manager server UI, alsoknown as meter manager monitor 710, which is outputted by meter managermodule 614 to a client device for display in a web browser window isshown in accordance with the present disclosure. The meter managermonitor 710 includes:

-   -   Security Login 772—Usage of Meter Manager Monitor requires a        login, that will be confirmed with the Meter Manager Server,        before software features can be used.    -   Cloud Configuration 770—UIs will enable a user to configure the        usage of the Cloud Server by Meter Manager, including login        information, meter registration, and meter upload options.    -   LogDb Storage Method—The user will be given the option of using        MS Access or Massive Table for meter log storage.    -   WebAPI RPC 750—RPCClient will be extended to use the new WebAPI        RPC protocol to interface with the meter manager Server 614/702.

Referring to FIG. 18, a flow diagram of the operation of a log viewer isshown in accordance with the present disclosure. Log Viewer 902 is anapplication, which provides access to viewing (i.e., in a UI outputtedfor display to a client device) the logs from multiple meter datasources, including the old MS-Access LogDb v3 and v4, as well assupporting newer data sources such as PQDif, ComTrade, Server Dbs,reading logs directly from meters 604, 606, and other data sources.Additionally, log events are shown by viewer 902 in a more integratedmanner, showing all data in a single Combined Event Viewer, which theuser can then filter or drill down to specific details and event types.Each event type also allows jumping to related events, such as PQ towaveforms and limits to system events, to make it easier for the user torapidly analyze the events. A user selectable number of meters will alsobe represented by each Viewer 902, allowing the user to analyze theissues which occur across a location.

Referring to FIG. 19, several features of cloud viewer or server 602 areshown in accordance with an embodiment of the present disclosure.

In one embodiment, the web server 904 is IIS, web service handler 906 isASP.NET, cloud server 602 is hosted on Azure and database will beSqlServer 2016. Historical channels will be stored in one table, with˜50 pre-allocated channel fields.

In another embodiment, the Cloud Viewer uses RabbitMQ as an internalmessaging queue, where the cloud server 602 is hosted on AWS (Amazon WebServices) and the database is InfluxDb.

Referring to FIG. 20 a flow diagram illustrating how several UIcomponents (904, 908, 910, 912) of system 600 in accordance with anembodiment of the present disclosure.

-   -   LogViewer/Dashboard 904        -   Logs 904A—Displays each of the logs in a drill down fashion.        -   Dashboard 904B—Displays an overview of each of the logs in a            single convenient page. Dashboards should include both raw            data trends, and ‘analysis’ dashboards, such as sum usage            for the day across multiple locations.    -   Reporting 908—Displays reporting options, and interface to view        automatically generated reports, and generate new reports. A        backend report generator is used to schedule and trigger the        automatic generation of reports.    -   Energy Billing 910—Linked to the reporting, Billing allows        configuring the billing components, including reports, and        displays generated bills and billing/cost related dashboard        information.    -   Realtime Data 912—Displays “realtime” meter data from an        internal database, kept up to date by data postings.    -   User Registration and Configuration—Allows for the registration        of new users, configuring user settings, and linking users to        customers.        -   Payment—Allows users to manage their payment for the            service, and view their current payments.    -   Location Management—Allows creation and modification of location        settings, including configuring meters.    -   Admin Management—Backend portal for maintainers to access all        features, plus directly edit security and payment systems, and        view audit logs.

In one embodiment, meter cloud system 600 implements public keyinfrastructure (PKI) certificates. By placing a PKI certificate on eachnode in the system, such as the cloud server 602, individual instancesof the meter manager module 614, and meters 604, 606 themselves, themeter cloud system 600 can provide a reasonably high level of confidencethat each node is talking to legitimate other nodes. By placing acertificate in each meter 604, 606 (and the meter manager module 614),the cloud server 602 can verify that the meter 604, 606 is known andlegitimate, preventing false or hijacked posts and queries to the server602. Certificates can also be used to encrypt data that is transferredbetween the nodes, the high security transfers, such as firmwaretransfers, and security actions, such as logging in, and changingsecurity parameters in meters 604, 606. Meter certificates are used toensure that a meter 604, 606 is legitimate and allowed to interact withthe cloud server 602. However, to maintain authenticity, thesecertificates need to be changed out periodically. This will be handledautomatically by the cloud server 602, which will both provision newcertificates, and retire old ones. Meter cloud systems 600 includes acertificate management UI for the system admin to review the existingcertificates and trigger changes.

In one embodiment, a web application firewall (or WAF) (e.g., webapplication firewall 810 described above) is provided that filters,monitors, and blocks HTTP traffic to and from the meter cloud server602. In contrast to a regular firewall, a WAF 810 filters the content ofspecific web applications while regular firewalls serve as a safety gatebetween servers. By inspecting HTTP traffic, the WAF 810 of the presentdisclosure may prevent attacks stemming from web application securityflaws, such as SQL injection, cross-site scripting (XSS), fileinclusion, and security misconfigurations. The WAF of the presentdisclosure may be deployed in front of the web applications, describedherein, and analyzes bi-directional web-based (HTTP) traffic-detectingand blocking anything malicious. This functionality can be implementedin software or hardware, running in an appliance device, e.g., a clientdevice, or in the server running a common operating system.

The WAF may be a stand-alone device or integrated into other networkcomponents. In other words, a WAF can be a virtual or physical appliancethat prevents vulnerabilities in the web applications of the presentdisclosure from being exploited by outside threats. Thesevulnerabilities may be because the application itself is a legacy typeor it was insufficiently coded by design. The WAF addresses these codeshortcomings by special configurations of rule-sets, also known aspolicies.

It is to be appreciated that the WAF 810 of the present disclosure maybe deployed inline in three different ways, i.e., transparent bridge,transparent reverse proxy, and reverse proxy. Transparent’ refers to thefact that the HTTP traffic is sent straight to the web application,therefore the WAF is transparent between the client and server. This isin contrast to reverse proxy, where the WAF acts as a proxy and theclient's traffic is sent directly to the WAF. The WAF then separatelysends filtered traffic to web applications. This provides the additionalbenefit of IP masking.

The meter cloud system 600 includes a system management interface(described in greater detail below) for use by system administrators(e.g., sales, engineers, admins, etc.) to view and manage theconfigurations and data of all customers. The system admin user is aspecial user type, which the meter cloud system 600 enables to accessthe system management webpages and configure the system on a globallevel. At the user management level, a user may view and configure allusers registered in the system, including the ability to reset/changepasswords, disable and ban users, create and delete accounts, and view auser's history. At the customer management level, a user may view andconfigure all customers in the system, including their billinginformation, billing history, and enabled features. At a metermanagement level, a user may view and configure all meters registered inthe system, including the ability to add or remove a meter to acustomer, change meter settings, and view meter data.

The meter cloud system 600 includes a security audit feature forensuring the security of a server. Not only does it provide regulatorycompliance, it can also be used for digital forensics after a breach,which can increase the confidence of customers. Additionally, it can beused to identify threat actors before they perform a breach, byidentifying malicious looking activity. The security audit may beperformed at the following levels:

-   -   Server Audit    -   Provide a server level audit, which logs all secure activity        across the entire server, including detailed source information.        This log is the basis, after filtering, for other security audit        logs. The audit provides forensics and helps identify security        threats to the cloud system 600. The audit may further be        reviewed by a threat analysis software. As such, it may be        exported in a common format, such as CEF and syslog.    -   Admin Audit    -   Server level audit for system admins provides commonly useful        information, such as logins, settings changes, and actions        performed. This audit helps review what changes may have        occurred on the system, as well as diagnose problems for        customers.    -   Customer Audit    -   The customer audit allows customer admins to review the changes        that have occurred to their customer, to review and keep tabs on        the users they manage, as well as providing a trail of changes        they themselves have made.

The meter cloud system 600 provides a report generation feature (as willbe described in greater detail below with respect to an energy billingmodule) that allows users to generate various reports, based off ofselected and configurable templates, on a schedule or manually. Thesereports base their data off the meter data which has been stored in theserver. A report template configuration UI, schedule configuration UI,and generated report viewer UI are provided. Exemplary reports include:

-   -   Custom Data export logs: Provides a csv format export file,        which contains the history of user selected channels for the        time range of the report, along with computed formulas applied        to rows, columns, and in the header. The report may contain a        number of channels from a number of meters.    -   Note, each row is a point in time, and each column is a channel        of a meter, or a formula.    -   Energy Usage report: Provides a pdf report which analyzes the        energy usage for a number of meters, and provides usage        information, summaries, trends, and comparisons between meters.    -   Custom Analysis report: Provides a csv format export file, which        contains analysis of meter data and information, along with        meter and facility specific information. Analysis data can        include billing rate fields, costs, usage, sums, averages, and        max/min values.    -   Note, each row is a meter or a facility, and each column is a        custom field.

A Report Viewer UI is generated in cloud server 602 and provided to aclient 608, which allows the user to view all the reports they havepreviously generated, delete old reports, and generate new ones. Storageis provided on the server for reports generated for each customer, witha time limit on age to minimize storage space requirements. A ReportConfiguration UI is provided, which allows the user to view, edit, andcreate report templates, as well as to create a list of reports togenerate based on the templates. Reports are scheduled and generated bya configurable list of reports to generate, which pairs a reporttemplate, set of meters, and schedule to generate on, together.

The meter cloud system 600 provides Energy Billing by adding ratestructures and bill generation as an enabled feature, based on theenergy readings uploaded to the cloud server. The application of theenergy billing is through, for example, the billing module, dashboardsand reports. Configurable bill templates allow the user to create anumber of bill generation templates, which include channels to bill offof, a schedule and duration, bill format, and rate structures to apply.A UI is provided to create, edit, list, and copy bill templates.Configurable rate structure templates allow the user to create anarbitrary number of configurable rate structures, which can then beapplied to bill templates to generate bills. A UI is provided to create,edit, list, and copy rate structures. Customizable rate plugin allowsfor the variance in regional rate structure requirements, implement ratecharges as easy to implement code plugins, with the goal of allowingtech support or software to quickly add rates on customer request,without requiring retesting the whole system.

In one embodiment, Bills are pdf reports which include a set of chargesbased on a rate structure template, along with basic usage history, andmeta data such as customer info, provider info, and user configurabletext. Customizable layouts provide the ability to customize the layoutof the bill report in the report template. Many customers requirealternate labels, additional text, additional fields, and differentlayouts, to match their expectation of a bill or invoice. UserSelectable time range provides the ability to generate bills for a userselected interval, down to an hour resolution.

A Dashboard Feature (implemented by a dashboard module of server 602described in greater detail below) provides analysis of log data, beyondjust presenting the raw log data, in a set of data fields and graphs. ACustom Dashboard Panel creates a dashboard panel that can be customizedby the user, to show the information they want. Options includes basedashboard type, source channels or logs, source meters, and analysistypes, as appropriate to the dashboard type. Exemplary dashboard typesinclude:

-   -   Per User: Allows custom dashboards that are unique to that user,        and displayed on their home page.    -   Per Facility: Allows custom dashboards that are unique to a        single facility, and displayed on the facility dashboard page.    -   Per Meter: Allows custom dashboards that are unique to a single        meter, and displayed on the meter dashboard page.    -   Dashboard Templates: Allows the user to create custom dashboard        templates, which they can then select when customizing a        dashboard panel, to quickly configure that panel.

In one embodiment, Dashboard Tiles are provided which are groups ofdashboard panels, where the user customizes the size and layout of eachpanel to suit their needs.

In another embodiment, Analysis Dashboards are a dashboard type thatanalyzes historical data, and provides summary information on that data,such as aggregations, avg/max/min, usage to date, sums, standarddeviation, and deviation between channels. Analysis of channel appliesthe analysis to a single selected channel, or the aggregation ofmultiple channels. Analysis of Facility applies the analysis to all themeters with the selected channel at a facility, or the aggregation ofall the meters at the facility.

Future Trend Prediction dashboards are a type that analyzes historicaldata, and provides a forecast of what will happen to that data in thenear future. Trends could be expressed as a percentage likelihood of atype of event in the near future, a forecast value in the near future,or a prospective trend over the near future. Comparison dashboards are atype which provides comparisons between different ranges in time,different channels, or between different meters.

Cost dashboards are a type which applies a selected rate structure to ameter or facility, and displays a breakdown of the costs involved.Exemplary cost dashboards include:

-   -   Cost Trend: Displays a graph of the costs over time. May not        include all costs, as some costs are not affected by time, such        as flat fees.    -   Cost Totals: Displays a breakdown of the costs for the current        time range displayed.    -   Cost Comparison: Displays a comparison of the cost breakdown        between multiple ranges in time, or between multiple meters or        facilities.

Realtime Dashboards are a type which, instead of displaying thehistorical logged values of a channel, display the current values postedby the meter (or within a reasonable time frame). Exemplary real-timedashboards include:

-   -   Live values from meters: To get live values from meters, the        meter (or meter manager module) polls the current values, and        posts them to the cloud server. These posted values are then be        stored for display in the real-time dashboards.    -   Value Dashboard Panels: Value Dashboard panels are a type of        real-time dashboard which presents one or more channels in a        semi-graphical format, such as a large single value, gauges,        bars, or colorized indicators.    -   Grid Dashboard Panels: Grid Dashboard Panels are a type of        real-time dashboard which presents multiple channels or multiple        meters in a grid format, to allow the user to quickly determine        values at a glance.    -   Internal storage of real-time values: Store the real-time values        in an internal array, whether a database or in memory, for a        limited period of time.    -   Short term history trendlines of real-time values: Along with a        live value, a small trendline of previous live values can be        displayed, allowing the user to identify trends at a glance.    -   User configurable limits on real-time values: Allows the user to        create warning limits on real-time values, such that if the        value is detected to be over or under a certain limit, an action        will be taken. When configured, the live value will be displayed        in a different color, or with a warning indicator next to it.        When configured, a notification will be displayed in a        notification bar for the user, to bring their attention to the        issue. When configured, the user will receive an email when the        limit is triggered.

A meter control feature allows a user to interact and control a meter,via the website. Since the cloud server cannot directly control a meter,the control is performed via a message queue which the meter (or metermanager module) periodically reads. The message queue holds, forexample, instructions, commands, etc., to be read (or downloaded) andthen executed by a meter. The Meter Control includes a UI interface,which provides both the ability for the user to control a feature, aswell as provide feedback on the status and success of the control. Ahistory of all control actions, and their results may be kept anddisplayed to the user. A Profile Update allows the user to update theprofiles of meters. These updates will be put into a queue, along with astatus feedback as to when those changes have been accepted, or thereason for being denied. To modify the profile, the current profile isread and stored. The current profile may be uploaded from the meter tothe server, and stored along with a modification date. A Profile UIprovides a UI that displays all the profile settings, and the ability tochange them, e.g., request a settings change for an individual meter,request a common settings change for a group of meters and allows theuser to create and store a set of profile templates, which can then beloaded into a single, or multiple, meters.

The meter control feature allows the user to perform resets of energy,demand, max/mins, and various different logs. Manual Reset requests afeature to be reset, and provide an update when it has been performed.For readings, such as energy and demand, the values must be posted tothe cloud server before the reset is performed. Similarly, logs must beposted to the cloud server before the reset if performed. Additionally,the user can set up a schedule, such as once a week, or once a month, toperform a reset of a specified feature.

The server 602 is configured to keep track of the firmwares of all themeters, along with the hardware configuration, and providerecommendations to the user on what meters should be upgraded. When theuser selects upgrade, the server 602 with transfer the appropriatefirmwares to the meter/s in question to be upgraded. Security Updatesallow the user to configure security on a meter, including configuringroles, users, and passwords. The ability to configure multiple meterswith the same security configuration is included.

The meter cloud system 600 employs centralized security, for example,synchronized security between cloud and meter, such a meter login usesthe same parameters as the cloud. Additionally, the meter may use asecondary query to the cloud for login, rather than storing the securityinternally. User Roles are provided to control feature access.Configurable user roles are added, which can then be assigned to usersunder a customer by the customer admin, to restrict what features andfacilities a user has access to. An extension of user roles, system userroles allows system admin users have restricted access to systemfeatures, such as only having read access to all meters or configuringsystems, but not allowing the deletion of users or billing information.

In one embodiment, billable extensions may be employed to restrictaccess to features based on whether the customer has paid for thefeature. A Billable Extension Selection UI is provided by server 602 tobe displayed on a client device to allow the user to enable or disablewhat features they want to pay for. The architecture of the system 600is configured to restrict UI access and usage of billable features, sothat they can only be used when enabled (and billed) for this customer.

Meter cloud server 602 is configured to generate and provide powerquality analysis reports (e.g., in a PDF or other suitable format). Thepower quality analysis reports analyze power quality events includinglimits, power quality, and waveform events, and provide informationabout those events. Exemplary reports include:

-   -   Single Event analysis report: Provides an analysis report on the        conditions and information surrounding a single event, or group        of events.    -   Multiple Event summary report: Provides a summary report of all        the power quality events which occurred in the time range of the        report.    -   Event Identification: Adds possible event issue identification        to the Power Quality

Analysis reports.

Meter manager module 614 and meter cloud server 602 integration featureswill now be described, such as, but not limited to, integrating the userconfiguration, registration, and log upload of meters 604 to the MeterCloud 602 from the meter manager module 614.

Meter manager module 614 provides a bridge for older (or legacy) metersor IEDs 604 to upload their log data 612 to the cloud server componentsof the meter cloud server 602. Additionally, the meter manager module614 simplifies the registration and maintenance of multiple meters 604with the meter cloud server 602, by automatically registering all foundmeters 604 with the meter cloud server 602.

The meter manager module/meter cloud integration provides four majorcomponents for the user to maintain their portion of the meter cloudsystem 600:

-   -   Meter Cloud User Integration and Configuration—This feature        includes an interface to configure what server to use for the        Meter Cloud 602, and what user information to login and use for        all other services. This feature may be used if the user doesn't        have a login for the Meter Cloud 602    -   Cloud Sync Service—This feature automatically registers all        meters to the entered user account, and automatically uploads        log data for meters which have been activated. This feature also        keeps the meter manager module 614 synchronized with the        information configured on the Log Viewer Cloud web server.    -   Meter Cloud Service Status—This feature provides a status and        history for the Cloud Sync Service.    -   Meter Configuration—The Meter Configuration is configured to        allow the user to enable and disable which meters are active in        the meter cloud server 602, as well as provide status        information on the log data which has been uploaded.

In one embodiment, the meter manager module 614 will not provide MeterCloud configuration options, such as customer configuration, userregistration, meter configuration (other than those listed), or locationconfiguration. These features may be left to the Log Viewer Cloud webserver, and links to the web pages will be provided.

Additionally, the meter manager module 614 is configured to provide someMeter Cloud Server functionality, including registering meters,receiving uploaded log data, and responding to queries for log data.This allows one meter manager module 614 to operate as a server foranother device, such as a client device.

The meter manger module 614 is configured with a plurality of features,including, but not limited to, using a user's login to register meters604, 606 and upload log data, providing links to web pages forconfiguring customers, locations, accounts, and meters, automaticallyregistering all meters in the meter list to the meter cloud server 602,providing tools for the user to enable or disable a meter in the metercloud system 600, automatically uploading log data for meters which areenabled in the meter cloud server 602, providing history and status forall registrations and log data uploads, synchronizing the meter managermodule information with meter cloud information.

As shown in the FIG. 21, the meter manager module 614 is configured toregister (948) a cloud ID created by a user (950) and sync (952) thecloud ID with the cloud server 602. Thereafter, the meter manger module614 queries (954) information stored in the cloud server 602 andregisters (956A, 956B) various meters. After the meters are registered,meter data is uploaded (958A, 958B).

Referring to FIG. 22, a system diagram showing the implementation of themeter manager monitor 702, meter manager service 980 of meter managermodule 614, and cloud server 602 are shown in accordance with thepresent disclosure.

The Cloud Sync Service 982 of the Meter Manager Service 980 is shown inFIG. 23 in accordance with the present disclosure.

The Cloud Sync Service Runner (CSSR) 982 is a queue based actor, similarto the ImportRunner. The CSSR provides most interactions with the MeterCloud for Meter Manager (the primary exception being the direct cloudconfig tools provided in the Monitor for editing and verifying Userinformation).

The CSSR is configured with several features listed below:

-   -   Upload Data 984—Uploads a meter's log data to the Meter Cloud.    -   Register 986—Processes registering and reconfiguring meters with        the Meter Cloud server 602.    -   Server Sync 988—Reads the current configuration for the        configured customer from the server, to ensure the meter manager        module operates on the most recent configuration.    -   Refresh Scan 990—CSSR 980 periodically compares the meter        information and cloud configuration available with what is        available in the cloud, and enqueues synchronizations and        uploads as necessary.    -   Status 992—Used to report on the status, inner workings and        cache, and history of the CSSR 980.    -   Cache 994—The CSSR 980 prebuilds all the statuses and values        into a cache 994, to enable rapid determination of what needs        actions and what doesn't. Each item in the cache 994 is tied to        an update time, which is used to determine if anything has        changed since the cache value was last updated.

The Cache 994 of the CSSR 980 n includes several modules, such as, MeterInfo UID, User Cloud Info, Current Status, and History.

Meter Info module includes features such as cloud configuration, Log Dbavailable, and Cloud Db available. Cloud configuration keeps track ofwhat meters have been registered with the cloud, if upload is enabled,and if the meter is enabled with the cloud. Log Db data is stored tokeep track of what log data is available from the meter's log db. Arefresh is triggered by log retrieval. Cloud Db data is stored to keeptrack of what log data has been uploaded to the meter's cloud db. Arefresh is triggered by an upload.

User Cloud Info is configured to store data and keep track of the cloudconfiguration for the configured user, including customer info, logins,enables, locations (if available), and meter configurations.

Current Status module is configured to store data to keep track of thecurrent status of the CSSR for the Status reporting component. TheCurrent Status module includes a current action feature, which providesinformation about the current action being performed. The current actionfeature will be blank if the CSSR is currently idle. The Current Statusmodule also includes a queue information feature, which provides a listof all actions that are pending in the CSSR action queue. These actiondo not include the currently executing action. The Current Status modulealso includes a Counts feature, which includes counts of actions whichsucceeded, failed, or were skipped because nothing needed to be done.

The History module is configured to store history of the actions whichwere attempted, including details on the parameters and results. Thedata in the History module is kept as an in memory queue of 1000 items.

The Meter Manager Service 980 further includes a Log Server, whichprovides access to the Log Databases for the meters, both to read data,and to push data into them (as part of meter manager module acting as ameter cloud server).

The Meter Manager system of the present disclosure includes thefollowing RPC commands to support controlling and querying the CloudSync Service:

-   -   cloud.meter.register    -   cloud.meter.upload    -   cloud.refresh    -   cloud.info—Returns the current cloud configuration info and        status.    -   cloud.sync.status    -   cloud.sync.history    -   cloud.user.verify—Verifies that the given user can login to the        cloud server, and is valid.    -   cloud.enable [user] [pass]—Attempts to configure the meter        manager scheduler to sync meters and configuration with the        given username and password. The user is verified to have        permission to configure the cloud for their customer.    -   cloud.disable—Disables cloud integration, clearing the user and        password cache.

Cloud Info—The following information is configured and cached by themeter manager module 614 to control how the meter manager module 614interacts with the Meter Cloud 602:

-   -   cloud.location    -   cloud.apikey    -   cloud.customer    -   cloud.user.name    -   cloud.user.pass    -   etheria.client˜enabled—[bool] Controls if meter manager module        614 is integrated with the cloud 602 as a client.    -   etheria.client˜host    -   etheria.client˜port    -   etheria.client˜rootpath    -   etheria.client˜user    -   etheria.client˜password

Meter Cloud Info—The following information is configured and cached bymeter manager module 614 to control how meter manager module 614interacts with the meter cloud server 602 for a specific meter (thesesettings are stored in the meters setting bag):

-   -   cloud.meter.uid—[string] Cloud UID for the meter. Assumes the        meter is not registered if not found.    -   cloud.meter.enabled—[bool] If this meter should be registered        with the cloud. If this is set, and uid is not, the meter should        be registered.    -   cloud.meter.upload.enabled—[bool] If this meter should upload        its log data to the cloud. A meter may be registered and not        upload.

The meter manager 614 includes a user interface supporting the followingfeatures:

-   -   Cloud User Configuration, which enables a user to log in and        provides several associated options    -   Cloud Meter Configuration    -   Cloud Sync Status, which enables a user to see one or more Meter        Lists, Scripts, and History Status

The meter registration process notifies the Meter Cloud 602 of a newmeter to store meter data, and associates it with a customer, so thatcustomer can view the meter's data. In one embodiment, when the meterfirst comes online, or when it is first discovered by the Meter Proxyserver, it attempts to self-register with the Meter Cloud 602, whichreturns a Meter UID (user identifier/identification) to be used foruploading meter data. Later, when a user registers as a customer in theMeter Cloud, they are provided with a Customer Key, which they thenregister with the Meter, or Meter Proxy server. The meter or proxy thenassociates itself with the customer using the Customer Key. This processis shown in FIG. 24.

In another embodiment, an alternate registration method would be for theuser to search for their meter's Meter UID or serial through the MeterCloud as shown in FIG. 25. The meter would still register itself withthe Meter Cloud, but after the user registers a new customer, they wouldbe provided with an Add Meter option, which would allow them to searchfor the meter using the serial or Meter UID.

The meter registration process of the present disclosure providessimplistic registration and association, so that users have to do aminimum of effort to bring their meter online in the meter cloud server602. In one aspect, meters self-register with the meter cloud server602, or through a proxy software. To associate the meter, a user entersa customer code to the meter, or a proxy software, to self-associate themeter with a customer; or alternatively, a user links meters tocustomers by searching for the serial or Meter UID through the metercloud UI.

Meter Registration—When a meter starts up, or is detected by the MeterProxy server, if it finds that it does not have a Meter UID for themeter, it attempts to register the meter with the Meter Cloud. Onceregistered, the Meter UID is stored for further use.

In general, the registration process preforms the following steps:

-   -   1. Register Meter—Sends the register meter api command to the        server. If the server already has the meter registered, it        responds with the meter info for that meter, including the Meter        UID. If the meter is new, the meter is registered, and the new        Meter UID is returned to the caller.    -   2. Initialize Database—When a new meter is registered, the        server database is initialized for that meter, and a new Meter        UID is generated for that meter.    -   3. Register Meter Info—After a meter is registered, important        meter settings, such as CT/PT ratio, Energy Scaling, and Hookup,        are written to the server.

Customer Association—When a user registers as a new customer, they mustfirst search and register for access to their meters before they canview them, using a UI provided to them via the Meter Cloud UI. Oncefound, they confirm that the meter is theirs, and it is added to theirmeter list, so that when they enable it, they can view data.

In general, the association process preforms the following steps:

-   -   1. Create Customer—Creates a new customer in the Meter Cloud        system.    -   2. Search for Meter UID—At any time, a management user for the        customer can go to the Search for Meter screen, and enter a        meter serial or Meter UID to search for. If the meter is found,        they can confirm that they own that meter: the server then        associates the meter with that customer, and it is added to        their meter list. Once enabled, they can then view the data.

Details on the user sub-system of the Meter Cloud, includingregistration, access levels, and deactivation will now be described.Referring to FIG. 26, an overview of the Cloud Meter user managementfeature of meter cloud 602 is shown in accordance with the presentdisclosure.

-   -   Key Terms        -   User—Someone who logs into the Meter Cloud to view meter            data, and configure the system.        -   User UID—The unique id of the user, used for internal            references and trackings.        -   User Role—Each user has a role in the Meter Cloud, which            controls what features they have access to.        -   Pending User—A user which has been created, but not accepted            into a Customer yet. Such a user can only access their own            information.        -   Limited User Role—The Limited User Role only allows a user            to view the data for the meters belonging to a Customer. The            subset of meters the user has access to can further be            limited to a set of locations.        -   Enterprise User Role—The Enterprise User Role has full            control over configuring the Customer and it's settings, and            has access to the data of all meters. Additionally, the            Enterprise User can edit the settings of other users, as            well as verify their registration with the Customer.        -   Customer Owner Role—The Customer Owner has full access to            all features of the Customer, as well as being able to            configure the billing information for the Customer.        -   System Admin Role—A special role, only given to the            manufacturer's users, which provides access to all meters,            customers, and users, as well as special administrative            interfaces for maintaining the system.        -   Customer—A customer is a group in the Meter Cloud, under            which multiple locations, meters, and users are configured.            One user is designated as the Customer Owner, usually the            user which created the customer.        -   Customer Key—A unique key generated for the Customer when it            is created. This key is used throughout the system to            associate meters and users with the Customer.        -   Meter Association—The process of linking a Meter to a            Customer, so that the Meter shows up in the Customer's meter            list, and users can access its data.        -   User Association—The process of linking a registered user            with a Customer, so that they can access the Customer's            meters.

The main features of user management will be described below:

-   -   Create User—When a user first creates their User in the Meter        Cloud, besides entering user information (such as username and        password), they can create a New Customer, or enter the Customer        code of an existing Customer.        -   Create New Customer—If the user selects Create New Customer,            a new customer will be created, and the new User will be            assigned as the Owner of that Customer.        -   Link to existing Customer—If the user wishes to link into an            existing Customer, they enter the Customer Key for that            Customer, and wait for one of the administrative users of            the Customer to approve the user.    -   Pending User—While a user is in the Pending state, they can only        edit their own settings. They cannot access any meters' data.        Once approved, they will be sent an email (if they configured an        email), notifying them.    -   Login—Once a user has been registered, they can then login, and        perform any actions they have permission for.    -   Perform Activities—The regular actions of the user, limited by        the roles assigned to the user.

In accordance with various embodiments of the present disclosure, thefollowing features are enabled via cloud 602:

-   -   Roles control what features of the Meter Cloud the user has        access to.    -   Customers are created when a user registers with the Meter        Cloud, if selected.    -   Each Customer has a unique Customer Key, generated when the        Customer is created, and accessible by all users from their user        settings page.    -   Users join customers by requesting to join, using a customer key        to find the customer. Enterprise users have the option to invite        other users, which sends them an email to register. The link in        the email automatically fills out the customer key and begins        the registration process.    -   One user is designated the Customer Owner, which is the only        user that has access to the billing information.    -   Users can only access the meters which are associated with their        Customer.    -   Meters are associated with a Customer by searching for the Meter        UID or Meter Serial.    -   Customers are isolated, such that a user can only access the        configuration and meter data associated with their customer. A        user can only be associated with one Customer.

In accordance with various embodiments of the present disclosure, thefollowing use cases are enabled by system 600:

-   -   Single User—Small companies and users testing the system might        only use one user, so one person would create the customer, edit        the billing information, configure the system, and view the        meter data results.    -   Tenant Users—Property managers would want to be able to share        the meter data for the locations with all of their customers or        tenents. In such a case, there might be only a couple enterprise        users, but they may have hundreds of limited users, which are        configured to view the meter data for their particular        locations.    -   Large Company—Large companies are most likely to distribute the        usage and configuration of the system across multiple users.        They may have dozens of enterprise users, configuring various        elements of meters and reports; and dozens of limited users,        collecting reports, and verifying the integrity of the system.

A customer is a group in the Meter Cloud, under which multiplelocations, meters, and users are configured. One user is designated asthe Customer Owner, usually the user which created the customer. Allcustomers are isolated, such that User A of Customer A can only accessthe meter data associated with Customer A, and User B of Customer B canonly access the meter data associated with Customer B. User A would notbe able to view the data of Customer B, and vice versa. Additionally,users can only be associated with one Customer.

Server 602 enables the association of a user with customers inaccordance with an embodiment of the present disclosure. Severalfeatures of user/customer association are described below:

-   -   Request Customer—When a new user is created, they have the        option of entering a Customer Key to request access to a        specific customer. If the Customer Key matches a customer, the        user is added as a Pending User, which has no access to the        customer until they are accepted.    -   Add Pending User—When the server receives a Pending User        request, it adds the new user to the list of pending users of        the customer, so that the Owner User can review that list, and        approve or reject the Pending Users. Additionally, the Owner        User is sent an email notifying them that there are new Pending        Users to review.    -   Owner Reviews List—The next time the Owner User logs in to the        Meter Cloud, they are notified that there are Pending Users to        approve. They review this list, and accept or reject Pending        Users, based on the user information that they provided.    -   Remove Pending User—If the Owner User rejects the Pending User,        that user is removed from the Pending Users list, and that user        must enter in a new Customer Key to request pending status        again. The former pending user is sent an email notifying them        that their customer request was rejected.    -   Add User to Customer—If the Owner User accepts the Pending User,        that user is removed from the Pending Users list, and added to        the Customer's User List. Additionally, the new user is assigned        the Limited User Role, until the Owner User can assign them the        proper role. Finally, the new user is sent an email notifying        them that their customer request was accepted.    -   Assign Role—After accepting a pending user, the Owner User        should assign a role to the new user, as they are given the        Limited User Role by default.

Several features of the meter cloud system 600 for Logs will now bedescribed in greater detail. The cloud server 602 supports receiving viaupload and storing several types of data log types, including HistoricalLogs, Waveform Logs, System Event Logs, Limit Logs, and Power Quality(PQ) Logs.

Historical Logs include historical data including a time series set ofrecorded data, organized by channel, and, in some embodiments, recordedat a specific interval. The table below includes exemplary historicaldata stored in Historical Logs:

W-hours in W-hours, the Interval, Timestamp Volts A-N Amps A ReceivedReceived Aug. 9, 2018 122.34 2.8 05:58:00 Aug. 9, 2018 122.61 2.7905:57:00 Aug. 9, 2018 122.7 2.8 05:56:00 Aug. 9, 2018 122.64 2.797,974,024.00 20 05:55:00 Aug. 9, 2018 123.04 2.82 05:54:00 Aug. 9, 2018123.12 2.8 05:53:00 Aug. 9, 2018 123.23 2.79 05:52:00 Aug. 9, 2018123.22 2.8 05:51:00 Aug. 9, 2018 123.13 2.82 7,974,004.00 21 05:50:00Aug. 9, 2018 123.11 2.8 05:49:00 Aug. 9, 2018 122.95 2.78 05:48:00 Aug.9, 2018 122.88 2.78 05:47:00 Aug. 9, 2018 123.05 2.79 05:46:00 Aug. 9,2018 122.84 2.8 7,973,983.00 20 05:45:00 Aug. 9, 2018 123.05 2.8205:44:00 Aug. 9, 2018 122.99 2.8 05:43:00 Aug. 9, 2018 122.9 2.8305:42:00 Aug. 9, 2018 122.47 2.82 05:41:00 Aug. 9, 2018 122.39 2.817,973,963.00 20 05:40:00

Waveform Logs include waveform recordings events which are triggered bymonitored conditions, such as a surge in voltage. When such an eventoccurs and is detected, the meter is triggered to record the individualsamples which make up the monitored readings, along with the triggerinformation, and logs this in a waveform recording. Multiple channelsare recorded, as well as the samples for cycles before and after theevent. The shape of this waveform is later used for quality analysis ofthe event.

For example, in one embodiment, the waveform data stored is representedas a graph with the y-axis relating to voltage and the x-axis relatingto time (e.g., in milliseconds). One such exemplary representation ofwaveform data is shown in the graph 1000 of FIG. 27. In FIG. 27, severalwaveform channels are overlaid in a single view. It is to be appreciatedthat, in one embodiment, the waveform data is not stored as an image,but as an array of values for each channel in the recording.

System Event Logs (e.g., stored in server 602 or a server/memoryaccessible via server 602) include system events, which are recordedwhenever an event which effects the operation of the meter occurs. Thesystem events stored may include events such as log retrieval, powerloss, settings changes, security events, and time changes. These systemevents are often used for auditing what is occurring with the meter. Thetable below represents an exemplary system event that may be stored inthe Log Cloud:

Date/Time Event Type Description Jun. 12, 2018 Device Start Up Firmwarev0032 17:29:34 Apr. 2, 2018 Device Start Up Firmware v0032 19:23:49

Limit Logs (e.g., stored in server 602 or a server/memory accessible viaserver 602) include limit events which are recorded whenever a readingchannel (the same set of channels as used in historical data) exceeds aconfigured limit, such as voltage going above 140v or below 72v. Whenthe reading returns to within a predetermined limit, the end of theevent is recorded. This allows the computation of a start time andduration of the event, as well as the worst excursion value for theevent. The table below represents an exemplary limit event that may bestored in the Log Cloud:

Start Duration Set Limit Date/Time (S) Index ID State Data Value SetPoint Jun. 22, 2018 37 1 Limit Below Volts 0 Below 108 09:15:06 2 A-N or90% Jun. 22, 2018 37 2 Limit Below Volts 0 Below 108 09:15:06 2 C-A or90% Jun. 15, 2018 598339 2 Limit Above Volts 191.16 Above 132 11:02:44 1C-A or 110%

PQ event logs (e.g., stored in server 602 or a server/memory accessiblevia server 602) include power quality events, which are recordedwhenever a high speed reading (the same set of channels as used inwaveform data) exceeds a configured or predetermined limit, such as the1 cycle voltage an exceeding 200v. When the reading returns to withinthe predetermined limit, the end of the event is recorded. This allowsthe computation of a start time and duration of the event, as well asthe worst excursion value for the event. The table below represents andexemplary power quality event that may be stored in Log Cloud:

Start Duration % of Full Date/Time ms Condition Channel Value Scale Jul.22, 2018 0 Sag VAN 94.45348 78.71124 09:32:32 Jul. 11, 2018 0 Sag VBN77.98228 64.98524 07:57:09 Jul. 7, 2018 1000 Sag VAN 87.5147 72.9289219:06:42

It is to be appreciated that PQ records are often taken at the same timeas a waveform recordings, and, in some embodiments, the two recordingsmay be linked. In addition, information about the meters themselvesshall be stored by the Log Cloud, to be used by the UI, reporting, andanalysis packages.

The meter cloud system 600 includes several security features. Thesecurity features are implemented because the cloud server 602 maysupport multiple customers simultaneously, and, therefore, the securityfeatures prevent users from one customer from accessing (intentionallyor otherwise), data from another customer.

The meter cloud system 600 also is configured with several storagefeatures to support that increasing number (e.g., tens of thousands ofmeters being deployed word wide and, in some instances, thousands justat one customer). The meter cloud system 600 storage features supportscalability and expansion of the system to store many data records formany meters, with little reconfiguration or performance impact on thesystem.

The different data types and data logs that meter cloud system 600 isconfigured to support (e.g., via being uploaded to the cloud server 602)will be described in greater detail below.

Meter cloud system 600 supports several types of Meter data and/orfeatures associated with interfacing with meters, including settings,uniqueness, time, and query, each of which will be described now.

Settings: Each meter includes settings associated to that meter. Thesesettings will be queried by reporting, UI, and the uploader, todetermine how to manipulate the Log Data. The supported meter datastored by Log Cloud includes, Meter Name (The display name of themeter), Meter Serial (The unique identifier of the physical meter),Meter Type (The hardware type of the meter), and Meter UID (The uniqueidentifier of the meter in the cloud system).

Uniqueness: Each meter includes a unique identifier (UID) in the LogCloud system, separate from the serial number of the meter. When metersare replaced in service, the serial number may change, but the UID willremain the same. This shall provide a continuity of measured data at alocation.

Time: Meters are installed all across the world, and thus the Log Cloudsystem storage and representation of these timestamps is configured tosupport multiple timezones. Timezone support may be implemented at anylayer, so long as it is self consistent. Meters times may be changed,which means duplicate timestamps may occur for different chronologicaldata. Both records must be preserved. Historical records which occurduring the rollback period of daylight savings time are preserved by theLog Cloud system as distinct values.

Query: Log Cloud system is configured to provide a query to read thesettings for each meter. The Log Cloud system is also configured toprovide a query to list all meters which the executing user has accessto.

Historical Logs and Historical Data implementation within the metercloud system 600 will now be described.

Historical data includes a time series set of recorded data, organizedby channel, and, in some embodiments, recorded at a specific interval.The supported channels may include one or more of:

-   -   Voltage AN    -   Voltage BN    -   Voltage CN    -   Voltage AB    -   Voltage BC    -   Voltage CA    -   IA    -   IB    -   IC    -   Frequency    -   Watts Total    -   VAR Total    -   VA Total    -   Power Factor    -   Interval Energy WattHr Received    -   Interval Energy WattHr Delivered    -   Interval Energy VARHr Received    -   Interval Energy VARHr Delivered    -   Interval Energy VAHr    -   Watts Positive Max Demand    -   Watts Negative Max Demand    -   VARs Positive Max Demand    -   VARs Negative Max Demand    -   VA Max Demand    -   Power Factor Positive Max Demand    -   Power Factor Negative Max Demand    -   Voltage A % THD    -   Voltage B % THD    -   Voltage C % THD    -   Current A % THD    -   Current B % THD    -   Current C % THD

It is to be appreciated that meter cloud system 600 is configured tosupport an increase in the set of channels supported to accommodate forfuture developments. In some embodiments, all meters will upload asimilar set of channels. Channels may be at different logging intervals.For example, voltage may be every 1 minute, and energy every 5 minutes.In some embodiments, an arbitrary sub-set of the supported channels maybe uploaded from a meter, as not every meter will be configured to logevery value.

With respect to data uploaded to the cloud server 602, no assumptionsshould be made about the order of channel data uploaded. For example,the meter cloud system is designed to support various changing uploadscenarios: Data may be uploaded in time sequence order, but need not be.Channels for a specific time range may be uploaded in the same post, butneed not be. The interval between data uploads may be around one day,but may be much slower (1 month), or much faster (15 minutes). Channelsmay be uploaded separately. Channels may be uploaded together. Data maybe uploaded in pages, repeatedly posting to cover large ranges of time.The meter cloud system 600 is configured such that each page will be anindependent post of data, fully self-consistent, and include all detailsnecessary to store the included data. The cloud server 602 is configuredsuch that separate channels may be uploaded in separate pages, as itcannot guaranteed that all data for all channels will be available atthe time of the upload for a specified point in time.

The cloud server 602 may be configured to implement a predeterminedupload format. For example, an exemplary upload format is shown below:

{ apikey: “~~~~”, meter_uid: “c4add118-b187-4d21-9813-d25bffdb6083”,channels: [ {chan_key:“reading.voltage.an”},{chan_key:“reading.voltage.bn”}, {chan_key:“reading.voltage.cn”} ],time_first: 1493590000000, time_last: 1493710000000, records: [[1493590000000,120.442184,119.7983875,119.8013317],[1493600000000,120.4224738,NaN,120.4119957],[1493610000000,120.1290346,119.5067033,119.8153032], ... ] }

The predetermined upload format is a format that associates a timestampwith one or more channel values. The format is selected such that theformat can be generated by an embedded device, thus complicated andproprietary communications stacks are avoided in the making the formatselection. The upload format is selected such that the format can easilybe transmitted over TCP and through a corporate firewall with minimumconfiguration on the part of IT. The upload format is selected such thatit supports ‘empty’ values, positions in the data array which are notfilled in, and do not need to be stored in the server. In oneembodiment, the format is configured such that ‘empty’ values are notrepresented by a valid value, such as zero. In this embodiment, where avalue is used, a invalid number is used, such as NaN.

Limits: The cloud server 602 makes certain assumptions about the databeing uploaded in Historical records. For example, it is assumed thatHistorical records shall be logged no faster than at One Minuteintervals. If the recorded data is faster, the uploader will reduce thedata to one minute intervals. Interval Energy computation period isconfigured as the logging interval.

All Historical values include the following formatting conditions: (1)All values shall be formatted as primary; (2) All values shall beformatted as doubles; (3) % values shall be formatted as 1=100%.

Cloud server 602 is configured with several storage features withrespect to Historical data. For example, in one embodiment, Historicaldata is stored according to one or more of the following conditions:

-   -   each recorded value is associated with a timestamp. A single        instance of multiple channels may be associated with a single        timestamp    -   Historical data is stored for at least 6 months    -   From 6 months to a year, the time frequency of the data can be        reduced to 15 minutes.    -   From 1 year to 2 years, the time frequency of the data can be        reduced to 1 hour.    -   Interval Energy cannot have its time frequency reduced. Interval        Energy data must be replaced with aggregated data over the        period it was reduced.    -   Long term full resolution storage should be provided in a        compressed, size reduced format. Long term full resolution        storage may be stored in a slow to access location and format,        such as raw binary files. Queries will be for blocks of data.        Data will be used for long term reports and analysis.

The cloud server 602 implements the following settings with respect tothe Historical data:

-   -   Scaled Energy Settings—These settings describe how the energy        should be formatted to provide consistency across softwares. For        example, with scaled energy, we may have a watthour value of        146789456 Wh, but the setting says to display it as 146.78 MWh,        or 000146.78 MWh. This format must be consistent between all        places that you can view the meter's settings    -   CTPT Ratios—Specifies the ratio and fullscale of Voltage and        Current    -   Hookup—Specifies what hookup type the meter is configured for,        which is used to determine which phase values are valid and        useful.

The cloud server 602 is configured to support sending/receiving severalqueries with respect to Historical data. Query speed for large ranges oftime is of paramount importance. Therefore, in one embodiment, thesystem is configured such that multiple channels are queried in onesession. Multiple channels may be requested in one query. In oneembodiment, the system is configured such that multiple months may bequeried in one session. Long ranges of time may be requested in a singlequery. In one embodiment, supports a query which lists all channelsrecorded for a meter. In another embodiment, the system supports a querywhich gets the time range for each channel of a meter. The end time ofeach channel may be used by the uploader to determine what data needs tobe uploaded.

Waveform Logs and Waveform Data implementation within the cloud system600 will now be described.

As described above, Waveform Logs include waveform recording eventswhich are triggered by monitored conditions, such as a surge in voltage.When such an event occurs and is detected, the meter is triggered torecord the individual samples which make up the monitored readings,along with the trigger information, and logs this in a waveformrecording. Multiple channels are recorded, as well as the samples forcycles before and after the event. The shape of this waveform is laterused for quality analysis of the event.

The cloud system 600 is configured to support at least the followingchannels in any waveform recording, though not required for everyrecording:

-   -   Volts AN    -   Volts BN    -   Volts CN    -   Volts AB    -   Volts BC    -   Volts CA    -   IA    -   IB    -   IC    -   Digital Inputs 0-7

The triggers for recording waveform recording include:

-   -   Sag—A sag is when the measured value drops too low. Sags apply        to Current and Voltage channels.    -   Surge—A surge is when the measured value goes too high. Surges        apply to Current and Voltage channels.    -   Input—An input trigger is a waveform capture that occurs because        one of the digital inputs changed state.    -   Manual Capture—The user triggered a capture of the waveform. A        manual capture is not associated with any channel, and has no        return to normal event.    -   Normal—A return to normal trigger occurs when the exception        condition, that triggered the original event, ends. Also known        as an event end, such as ‘Sag End’, or ‘Surge End’.

The cloud system 600 may be configured such that waveform recordings areuploaded one recording at a time. The uploads for waveform recordingsmay be in a predetermined format. An exemplary predetermined format forwaveform recording uploads is shown below:

{ “header”:{ “start_time”:1476702701196, “end_time”:1476702702192 },“trigger”:{ “freq”:58.348, “Van”:7119.540, “Vbn”:14336.721,“Vcn”:14593.935, “Vab”:18904.328, “Vbc”:25040.207, “Vca”:20157.926,“Vaux”:14631.782, “Ia”:5044.235, “Ib”:4068.405, “Ic”:6035.858,“Ix”:4996.338, “Imeasure”:756.134, “sample_interval_ms”:0.3906250,“trigger_time”: 1476702701250,“waveform_trigger”:[“Van=Sag_start”,“Van=Surge_end”,...,null] }“sample”:{ “digin”:[[1,1,1,1,1,1,1,1],...], “Ia”:[−4984.039,...],“Ib”:[5443.298,...], “Ic”:[−2154.510,...], “Iaux”:[52867.188,...],“Van_Vab”:[−10210.957,...], “Vbn_Vbc”:[10187.402,...],“Vcn_Vca”:[10387.617,...], “Vaux”:[0.000,...] } }

The predetermined waveform record upload format may include thefollowing information: Trigger Cause, Trigger Time, Recording StartTime, Time per sample, Total duration, Samples per cycle, List ofsamples per channel, List of RMS values for the cycle at the time of thetrigger. In some embodiments, the time resolution is at least 1 ms. Insome embodiments, the time resolution is at least 100 μs. A time neednot be associated with each sample, as the time of the sample can becomputed from the time of the start of the capture, and the time persample. In one embodiment, the cloud system is configured such thatAnalog Channels (Voltage, Current) are encoded as arrays of doubles inprimary and Digital Channels (Digital Inputs) are encoded as arrays ofarrays of 0s and 1s, representing the binary state nature of digitalinputs. In the cloud system, the Trigger block describes the datastructure of the information during the cycle of the trigger, includingRMS values, sample times, and any triggers that occurred during. The“waveform_trigger” in the exemplary predetermined format shown above isa list of triggers that occurred during the triggering cycle and is thelist of triggers for this waveform recording.

The storage within cloud system 600 of waveform records is such thatwaveform recordings are quickly accessible for at least a predeterminedperiod of time (e.g., 1 month) and slower access is acceptable forwaveform recordings that are at least a second predetermined period oftime old (e.g., 1 year old). Waveform records older than the secondpredetermined period of time (e.g., a year old) are stored in long termcold storage for analysis purposes.

Limiters: The cloud server 602 makes certain assumptions about the databeing uploaded. For example, it is assumed that there shall be no morethan 2048 samples per channel per recording. If there are more than 2048samples per channel per recording (or whether the data received exceedsany other predetermined limit), the software on cloud server 602 willattempt to truncate the recording (or other type of data received) toone cycle before the trigger, and as many after as available. Anotherassumption is that a sample rate of up to 256 samples per cycle shall besupported. If the sample rate is higher, the software will attempt todown sample the recording to 256 samples per cycle. Another assumptionis that the number of waveform recordings in a given period of timeshall be limited. For example, in one embodiment, the following limitsare implemented: (1) No more than 1 recording per second; (2) No morethan 5 recordings per minute; (3) No more than 25 recordings per hour;(4) No more than 50 recordings per day.

The cloud system 600 implements the following settings with respect tothe waveform records: Nominal Frequency, CTPT Ratio, Current Class,Fullscales.

The cloud system 600 is configured to send/receive a query to list allrecordings during a specified period of time. Responsive to the querythe system returns a list including the following for each record:

-   -   Timestamp    -   Triggers

The cloud system 600 is configured to send/receive a query to read backa single waveform recording. The format of the response may be similarto the upload format. The format may be a format easily usable inJavaScript for rendering on a UI. The query will use information fromthe list query to determine which recording to return.

System Event Logs and System Event Data implementation within the cloudsystem 600 will now be described.

System Events include values, where the following field may be recorded:Time, Event Code, Description. The event types may include, but not mebe limited to,

-   -   Programmable Settings Change    -   Device power loss    -   Device reset    -   Time changed    -   Firmware changed    -   Log reset    -   Energy reset    -   Max/Min reset    -   User login    -   User configuration change    -   Error reporting

In one embodiment, System Events may be uploaded in a predeterminedupload format. An exemplary predetermined upload format for SystemEvents is shown below:

{ “header”:[ “time”, “event_type”, “event_subtype”, “description”,“records”:[ [1482255759160,1,1,“device power off”], [1482255765000,1,1,“device power off”], [1482395650360,2,1,“updateprogrammable setting”], ...,[ ]], “time_first”:1482255759160,“time_last”:1482395650360, }}

The predetermined upload format for System Events is selected such thatthe format associates a single event with a timestamp and multipleevents may have the same timestamp.

Limits: The cloud system makes certain assumptions about the data beinguploaded in System Events. For example, it is assumed that Log RetrievalEvents will not be uploaded.

The cloud System is configured to support sending/receiving severalqueries with respect to System Events. For example, the system supportsa query which provides all events for a specified time range. Aspecifier for specific event codes to return may be included in thequery. The format of the query response may be the same proposed uploadformat above. The format is configured to be easily readable byJavaScript for listing on a UI.

Limit Logs and Limit Event Data implementation within the cloud systemwill now be described.

Limit Logs include limit events which are recorded whenever a readingchannel (the same set of channels as used in historical data) exceeds aconfigured limit, such as voltage going above 140v or below 72v. Whenthe reading returns to within a predetermined limit, the end of theevent is recorded. This allows the computation of a start time andduration of the event, as well as the worst excursion value for theevent.

The values that may be included in a limit event include:

-   -   Start time    -   Duration    -   Exception Channel    -   Exception Type    -   Worst case exception value    -   Worst case exception percentage

In one embodiment, limit events may be uploaded in a predeterminedupload format. An exemplary predetermined upload format for limit eventsis shown below:

{“header”:[“start_time,“duration”,“channel”,“limit_id”,“exception_type”,“except_value”,“except_percent”,“limit_threshold”], “records”:[[1477326041773,null,“readings.voltage.an”,0,0,40,23.49.84,80],[1477326040273,1.412,“readings.voltage.an”,1,1,148.54,122.72,120] ]“time_first”:1482255759160, “time_last”:1482395650360, }

Limits: The cloud system makes certain assumptions about the data beinguploaded in limit events. For example, it is assumed that only pairedlimit events shall be uploaded. Unpaired records shall be uploaded whenthey become paired. Unpaired start records shall be uploaded if nopossible end unpaired record is possible. It is also assumed that thenumber of PQ records in a given period of time shall be limited to (1)No more than 2 records per second; (2) No more than 10 records perminute; (3) No more than 50 records per hour; (4) No more than 100records per day.

The cloud system is configured to support sending/receiving severalqueries with respect to Limit Events. For example, the system supports aquery which provides all events for a specified time range. A specifierfor specific limits to return may be included in the query. The formatof the query response may be the same proposed upload format above. Theformat is configured to be easily readable by JavaScript for listing ona UI.

The cloud system may support Fullscales settings with respect to limitevents.

Power Quality Log and Limit Quality Event implementation within thecloud system will now be described.

PQ event logs include PQ events, which are recorded whenever a highspeed reading (the same set of channels as used in waveform data)exceeds a configured or predetermined limit, such as the 1 cycle voltagean exceeding 200v. When the reading returns to within the predeterminedlimit, the end of the event is recorded. This allows the computation ofa start time and duration of the event, as well as the worst excursionvalue for the event.

The values that may be included in a PQ event include:

-   -   Start time    -   Duration    -   Exception Type    -   Worst case exception value    -   Worst case exception percentage

In one embodiment, PQ events may be uploaded in a predetermined uploadformat. An exemplary predetermined upload format for PQ events is shownbelow:

{“header”:[“start_time,“duration”,“channel”,“exception_type”,“except_value”,“except_percent”,“pq_threshold”], “records”:[[1477326041773,null,“readings.voltage.an”,0,40.23,49.84,80],[1477326040273,1.412,“readings.voltage.an”,1,148.54,122.72,120] ]“time_first”:1482255759160, “time_last”:1482395650360, }

-   -   start_time: [long] Time the pq event started (exception was        first detected). Value as milliseconds since 1970.    -   duration: [double] The duration of the pq event in seconds. Will        be null if no end event was recorded.    -   channel: [string] The key of the channel the pq event occurred        on. PQ events will only occur on the following channels.    -   readings.voltage.an    -   readings.voltage.bn    -   readings.voltage.cn    -   readings.voltage.ab    -   readings.voltage.bc    -   readings.voltage.ca    -   readings.voltage.aux    -   readings.current.a    -   readings.current.b    -   readings.current.c    -   readings.current.n    -   exception_type: [int] The type of exception that triggered the        PQ event.

code event 0 sag 1 surge

-   -   except_value: [double] The worst observed value on the specified        channel during the event.    -   except_percent: [double] Value in percentage of fullscale, of        the worst observed value on the specified channel during the        event.    -   pq_threshold: [double] Threshold setting for the specified        channel at the time of the event.

Limits: The cloud system makes certain assumptions about the data beinguploaded in PQ events. For example, it is assumed that only pairedevents shall be uploaded. Unpaired records shall be uploaded when theybecome paired. This means that PQ records may be uploaded out of order.Unpaired start records shall be uploaded if no possible end unpairedrecord is possible. Another assumption is that the number of PQ recordsin a given period of time shall include predetermined limits such that(1) No more than 10 records per second; (2) No more than 30 records perminute; (3) No more than 100 records per hour; (4) No more than 200records per day.

The cloud system is configured to support sending/receiving severalqueries with respect to PQ Events. For example, the system supports aquery which provides all events for a specified time range. A specifierfor specific limits to return shall be included in the query. The formatof the query response may be the same proposed upload format above. Theformat is configured to be easily readable by JavaScript for listing ona UI.

The cloud system may support Fullscales settings with respect to PQevents.

The cloud system is configured with several security features. The cloudsystem is configured such that querying data and configuring the systemis only allowed by authorized user. The requirement for userauthorization is enforced at the API layer and not the UI layer. Thecloud server 602 is further configured such that all user and meters areorganized under customers and a user may be associated with one or moremeters. The user association may be configured such that a user may onlybe associated with meters for the customer they belong to and/or a usermay only query data for meters they are associated with. The cloudserver 602 is configured to provide a mechanism to prevent data frombeing uploaded from unauthorized users for a meter. In one embodiment,the cloud system is configured such that at least one user is designatedas the administrator for a customer. The cloud system is configured suchthat the customer administrator is able to configure all the meters forthe customer, enable or disable the usage of a meter in the cloud forbilling purposes, delete data associated with a meter, and/or view thedata for all meters for a customer. In on embodiment, the cloud systemis configured such that at least one user is designated as theadministrator for the system. The cloud system is configured such thatthe system administrator has access to configure and view all meters forall customer, to configure and view all users for all customers, and toconfigure and view all customers.

The cloud system 600 is configured to support the increasing number ofmeters deployed world-wide (e.g., thousands just at one customer). Thecloud system is configured to be easily expandable and scalable by beingdesigned such that minimal reconfiguration to increase the number ofsupported meters is required and minimal performance impact occurs withincreasing quantities of data. Each meter in cloud system 600 isassociated to a specific customer.

Each meter in the cloud system 600 is configured to employ severalstorage requirements to make the meter cloud system easily scalable andfunctional. In one embodiment, each meter in meter cloud system isconfigured to record at least 30 channels of historical data, at least15 minute intervals for historical data at least 10 waveform records perday, at least 20 limit records per day, at least 20 system event recordsper day, at least 50 PQ event records per day. In one embodiment, eachmeter is configured to store at least 6 months of recorded data. Thestorage each meter employs is optimized for fast query of large rangesof time series data.

The meter cloud system is designed to store the data of tens ofthousands of meters, including historical channels, system events, PQ,limits, and waveforms. However, this storage is limited, and someconfigurations can lead to hundreds of thousands of these records in asingle day, which if left running for too long, would quickly exceed thecapability of the storage. While there are some circumstances where thisdata is legitimate, in most cases this is poor configuration, or onlyfor debug purposes.

To counter this, the meter cloud system 600 limits the number of logsand/or records that can be uploaded in any particular period of time.However, without good feedback to the user that data may be missing fromthe data they view on the website, the user would only think that thesystem is broken or some type of error occurred.

A Limitor Notification is provided, which is a propagation of the countsand times of skipped data, up to the cloud server 602, so that thewebsite can display error count notifications to the user. An overviewof the Limitor Notification module 1050 is shown in FIG. 28 inaccordance with the present disclosure. Module 1050 may be stored inmeter manager 614, server 602, and/or any one of meters 604, 606 andexecuted by one or more processors in each of 614, 602, 604, 606.

When the meter log data is loaded by Loader 1052 from meter log database1051, it is passed through a Limitor filter 1053, which keeps track ofvarious conditions, and if the data violates that condition, it iseither modified or dropped, i.e., excluded from being uploaded. Forexample, in one implementation, those conditions could include thenumber of records in a single hour. As another example, waveform recordscould be limited to only 20 per day. As another example, waveformrecords could be modified to use a lower sample rate, or less cycles. Asanother example, historical records could be limited to at the fastestevery 1 minute. A count of limit violations each day, is kept per log.

All log data which passes the Limitor 1053 are included in a Data Page1054, which includes Limit Information 1055 about what was modified,which will detail the number of records skipped during the period ofthat data page. This package is then uploaded to cloud server 602, whichsplits and stores the information separately as Data 1058, and LimitCounts 1057. UI notification 1059 is then displayed to the user wheneverany data 1058 has corresponding Limit Counts 1057. When displaying arange of log data, whether it be historical, system events, orpq/waveform, the UI notification 1059 displays an indication, e.g., anexclamation mark, if the limitor count exceeds 0. Additionally, queriesfor the log data will also include the exception count for the range inquestion.

The Limitor Notification of the present disclosure provides for thefollowing features: detect and count daily log record limitor exceededconditions, and upload those counts to the server; store the limitorexceeded counts on the server; and display those counts to the user, forthe meter, log, and time range they are currently viewing. It is to beappreciated that the associated meter is not modified, nor the localmeter log database, if the upload is affected by the limitor. Thelimitor only modifies what is uploaded to the cloud server 602. Themeter log data that is not uploaded may be accessed from the meter, at alater time via various methods.

In one embodiment, cloud server 602 is configured to determine if meterdata (e.g., log data) pushed from meters 604, 606 and/or meter manager614 to cloud server 602 exceeds a predetermined limit (e.g., in datasize) and, if the predetermined limit is exceeded, server 602 excludesthe meter data from being stored in at least one database of server 602or a database server 602 is in communication with. In one embodiment,server 602 is configured to store only a predetermined portion of themeter data (e.g., a portion at or below the predetermined limit) in thedatabase if server 602 determines the meter data is above thepredetermined limit. Server 602 is configured to record a count andassociated time of day when the meter data was excluded, such that thecount and associated time of day of the exclusion of data can bepresented to the user via a web page (e.g., provided to client device608).

In one embodiment of the present disclosure, the meter cloud server 602,includes an energy billing module 1100. The energy billing module 1100is configured to provide bill analysis and cost report generation for aplurality of IEDs coupled to the meter cloud system of the presentdisclosure using energy data uploaded to the meter cloud server. Theblock diagram of the energy billing module 1100 is shown in FIG. 29 inaccordance with the present disclosure.

Energy billing module 1100 includes four components or modules:

-   -   (1) Settings Editor 1102: This module configures various        parameters and features of energy billing module, such as, but        not limited to, rate structures, reports, locations, etc.    -   (2) Internal Log Data 1104—This module includes one or more        memories configured to store energy usage data received by IEDs        coupled to the Meter Cloud system of the present disclosure. The        data stored may include meta information stored about the log        data.    -   (3) Dashboard Viewer 1106—This module is a UI configured to        generate and output for display a dashboard of log values stored        in internal log data module. The dashboard viewer may further        generate and output for display analysis (e.g., various trends,        calculations, or other types of analytics) of the log values        displayed.    -   (4) Reporting 1108—This module generates configurable CSV and        PDF reports, for example, the reporting module may be configured        with one or more modules for generating custom CSV files and PDF        files, such as a custom CSV module, a usage trending PDF module        (e.g., for generating a customized PDFs including usage trend        information associated with the loads one or more IEDs are        coupled to) and a bill PDF generator module (e.g., for        generating customized PDFs including billing information        associated with the loads one or more IEDs are coupled to).

In one embodiment, the log data is configured to enable a user tokeeping track of invalid billing values and enable the user to enter incorrections (e.g., via user input to a UI of energy billing module) toexisting data entries stored in log data module. In another embodiment,log data module may be configured to aggregate or organize data storedwithin log data module based on one or more characteristics orproperties of the data stored. For example, in one embodiment, log datamodule may be configured to aggregate energy usage data values for allIEDs or meters at a specific location or a group of locations. Othercharacteristics or properties may include dates/times, groups of meters(regardless of locations), load types, etc.

In one embodiment, dashboard module 1106 is configured to generatesummaries and analysis of energy values. The summaries and analysisgenerated may include:

-   -   Summed usage for the day    -   Comparison of usage for locations    -   Cost graph by hour/day (using the billing configuration)    -   Temperature logging and graphing in comparison to usage    -   Top demand lists

Reporting generator or module 1108 is configured to generate fullyconfigurable reports (e.g., according to user settings stored insettings editor). The reports may be generated on a schedule (once aday, month, etc.).

The data stored in log data module 1104 may be organized into Customers,Locations, and Meters. Customers are the top level, and contain a listof Locations. Each Location contains a list of Meters. Virtual Meters(e.g., data holders or containers) for each location aggregate the datafor all the meters at a location. Software Usage Accumulation isperformed on the Virtual Meters to provide previous and current usagevalues for Virtual Meters (e.g., summing the interval energy for allmeters as a location and using the sum as a single value) to be used inBills and Custom Reports. Meter data can be marked as negative, tosubtract the usage from the Virtual Meter aggregation. It is to beappreciated that Temperature Data logged for each location may be usedby dashboard module and provided in customized reports generated byreporting module.

In one embodiment, each meter or TED can load the data for a number ofchannels, mapping those data channels to billing commodities. Meters inenergy billing module 1100 need not have a one-to-one mapping withactual physical meters. Imports can be performed by energy billingmodule 1100 from a CSV file, or multiple meters can be imported byenergy billing module from a single physical meter's database.

In one embodiment, energy billing module 1100 is configured toautomatically detect errors in meter data stored or received. The errorsare flagged for user attention before bill are generated from that data.The meter data can be modified via user input to energy billing moduleto correct errors, and this is reflected in cost analysis and reports.However, the original value (i.e., the value flagged as being erroneousor incorrect) is retained, for auditing purposes.

Reporting generator or module 1108 is configured such that billing isapplied to commodities, applying a configurable Rate Structure to thecommodity data. Rate Structures include Fixed Charges, which are summarycharges: including Tiered Rates, Peak Demand, Taxes, Flat Rates, andCoincidental Peak Demand. Rate Structures include Rate Charges, whichare Time of Use based charges, configured using a perpetual calendar,and applied to the time of day the usage occurs within. The billing maybe divided into separate time intervals, e.g., up to 12 seasons (or anyother divisible time interval) to allow for separate rate charges atdifferent times of year.

The energy billing module 1100 includes several features, which will bedescribed below.

The energy billing module 1100 is configured to use energy data importedinto the meter cloud server 602 to generate cost dashboards and reports.The imported data may be marked by energy billing module 1100 togenerate cost dashboards and reports. The data channels may be marked bythe energy billing module 1100 as negative to subtract from locationusage aggregations performed by reporting module. For example, a usermay mark or apply a negative to a channel so these values may be removedfrom the sum. The energy billing module may further be configured toanalyze energy data for errors that would prevent generating a correctbill. If one or more errors are detected by energy billing module, oneor more users may be provided with a notification that the error(s)detected need correcting.

The energy billing module 1100 includes a settings configuration modulehaving an interface (e.g., viewable via dashboard module) for theconfiguration of perpetual rate structure to be applied by energybilling module to locations for cost analysis and report generation.Reporting module 1108 is configured to automatically generate MonthlyBill Reports for each location that has a rate structure configured, andemail (or otherwise provide) to the configured users. Reporting module1108 is configured to automatically generate Monthly Executive SummaryUsage Reports for each location, and email (or otherwise provide) to theconfigured users. The energy billing module 1100 includes an interface(e.g., dashboard module 1106) for the configuration of custom usagereports). Reporting module is configured to automatically generateCustom Usage Reports, and email (or otherwise provide) the generatedreports to the configured users.

The dashboard module 1106 is configured to show (via an output to adisplay) the energy usage for each meter and the summary energy usagefor each location. The dashboard module 1106 is configured to show thecost breakdown for each meter and location (using the rate structure forthe location), weather information logging on an hourly basis for eachlocation, and notifications when usage and cost exceeds a configuredlimit within a period. In one embodiment, the energy usage for aparticular meter over an adjustable period of time may be illustrated asa heatmap, as shown in FIG. 36. In this embodiment, a scale 3602 ofvarying colors is associated with varying levels of usage and theheatmap 3600 includes an x-axis 3604 indicating time of day and a y-axis3606 indicating days of the year. Usage by color is then displayed onthe heatmap 3600 in the appropriate location, e.g., 8:00 am on Jul. 1,2019. The heatmap may predict the usage for a predetermined number ofdays out from the current date and will show the predicted usage in theheatmap.

Energy billing module 1100 is configured to be useful in a variety ofuse cases, each of which are described in greater detail below.

Cost Trending: Report module 1108 is configured to generate reportsincluding cost analysis and cost trending (e.g., forecasting futureenergy costs based on current energy consumption data). The costanalysis features may be used to compare the usage between locations(such as buildings on a campus), and over time, to provide a sense ofcompetition, and incentive to reduce usage. The dashboard module 1106may be used to view the analyzed data to compare the usage across alllocations, trends of individual locations over time, usage analysisreports comparing the qualities and costs of all the locations, andalarms when usage exceeds configured limits. In these scenarios, theremay be many users that would login under a read only role, to view theirdashboard information in dashboard module. Such users often prefer tosee additional usage meta-analysis, such as usage per day, average peaktimes, carbon footprint, temperature comparisons, and track commoditiesother than just electricity, such as BTU's and gallons of steam. Each ofthe usage meta-analysis data described above may be generated byreporting module and displayed in dashboard module 1106 to be viewed byone or more users.

Sub-Metering: Reporting module 1108 is configured to provide severalfeatures that may be useful in sub-metering contexts (e.g., Malls,office buildings, etc.). For example, some property managers, whichsub-let out parts of buildings (such as malls), or entire buildings(such as office buildings), use the billing features of reporting module1108 to generate cost invoices, that are forwarded by energy billingmodule to the renter to specify the portion of the energy usage that therenter is responsible. In addition to costing, these users often want tosee daily usage reports emailed for tracking purposes. The energybilling module 1100 is configured to provide the reports generated(including daily usage reports) to one or more users via email or anyother protocol via one or more communication networks.

Event Hosting: Reporting module 1108 is configured to provide severalfeatures that may be useful in event hosing contexts (Corporate Events,Concerts, etc.) For example, a sub-category of property managers, theseusers sub-let out their property for short periods of time: sometimes acouple days, sometimes only a couple hours. They need to generate a costinvoice for specific short periods of time, with changing customersreceiving the invoice. Reporting module is configured to provide reportsfor event hosting contexts by generating reports including cost invoicesfor specific short periods of time for changing customers. The reportsincluding the invoices are then sent to the desired customers (e.g., thecustomers being billed for the short periods of time of energy usage).

External Billing Package: Reporting module 1108 is configured to provideseveral features that may be useful in event hosing contexts (LargeCompanies, etc.) For example, some companies have their own billingpackages that they use, but that require usage values to be entered infor costing and analysis. Reporting module 1108 is configured to enablethese users to use a custom reports module to generate a monthly reportthat they can import.

The cloud system 600 integrates an enabled usage-based payment orlicensing system in the cloud server 602, with an internal cloudmanagement software. The act of billing and account management will behandled by an automatic billing system. The automated billing systemwill use the cloud management software to enable the meters a customerdesires. At the beginning of each year, or when a user's account isfirst enabled, a usage report will be generated that can be fed into thesoftware that an accounting system uses for invoices. If the customerdoes not pay the yearly invoice by the expiration date, the meter willautomatically be disabled. After the customer's account has been set up,the number of meters a customer has enabled can be increased ordecreased.

Referring to FIG. 30, a flow diagram for the usage-based payment systemof cloud server 602 is shown in accordance with the present disclosure.The flow diagram of FIG. 30 includes the following steps detailed below:

-   -   Meters Registered 1202: Meters are registered from meter manager        module, or directly from the meter itself. However, at this        point, the meter is not enabled, and the user cannot access the        data that has been uploaded.    -   Customer Calls System Admin 1204: To enable access to meters,        the customer contacts a system administrator, e.g., an entity        that implemented the cloud system, to set up an Energy Cloud        Billing Account. This may be through, for example, an e-mail,        webpage interface, etc.    -   Setup Account 1206: The accounting system works out the details        of the customer's account with the customer.    -   Enable Meters 1214: Once the customer's account has been set up,        the system enables the meters requested by the customer.    -   Meters Accessible 1216: Once enabled, the customer now has the        ability to access the data of their meters.    -   Generate Usage Report 1208: At the end of every year, the        accounting system will go into the cloud management software,        and generate a usage report for each customer. From this usage        report, accounting will generate an invoice for the customers        usage for the next year.    -   Invoice 1210: The invoice previously generated will then be sent        to the customer for payment (121). If they do not pay, meters        will automatically be disabled at the end of the expiration        period.

The accounting system enables the following features: Certificates usedto ensure security between software and server; ability to enable anddisable meters on a per customer basis; ability for tech support toreview and manage customers, users, and meters; ability to query andgenerate monthly usage reports for each customer, for accounting billingpurposes, on demand. The user may request any month at any time; processdocument provided for accounting and tech support for how to managebilling.

It is to be appreciated that each meter will have an expire date, andcharges will be on the number of months in a year the meter shall beenabled for. Customers will pay for the upcoming months they plan onusing. Charges will be prorated for the remainder of the month inquestion, since enable. Meters will automatically be disabled if theexpiration period elapses, without being renewed. Customers will bebilled via an invoice from the accounting system, which bases the chargeoff a usage report generated from the management software. Theexpiration date of each meter will be presented in the managementsoftware, so that accounting can determine when to ask customers forrenewals. An upcoming renewals feature will list the renewals that arenecessary in the next month.

In general, there are two types of API calls, which are restricted bywho is capable of calling them, and the results when they are called bydifferent levels users. The at least two user levels are:

-   -   Admin—All of the following api's should only be able to be        called by a logged in system admin user.    -   General—The following api's can be called by anyone, but when        called as system admin, should provide access to meters under        all customers.

Below are exemplary commands with the user level in brackets:

-   -   Set Meter Expiration Date [admin]    -   Set the expiration date for the specified meter. If the        expiration date is blank, then the date is cleared, and the        meter is disabled. Alternatively, a low date can be used for        disable.    -   List Meters [general]    -   Modify to include the expiration date for the meter. If in the        past, blank, or missing, the meter is not enabled.    -   Modify to return all meters for all customers, including ones        not registered to a customer, for the system admin account.    -   List Users [general]    -   Lists users, and their information.    -   For general users, returns only their own user.    -   For customer admin users, returns the list of all users for this        customer.    -   For system admin users, returns the list of all users for all        customers.    -   List Facilities [general]    -   Lists facilities, and their information.    -   For general users, returns only the facilities they can access.    -   For customer admin users, returns the list of all facilities for        this customer.    -   For system admin users, returns the list of all facilities for        all customers.    -   List Customers [admin]    -   Lists all of the customers currently registered, and their        information. Note that the customer object is just the user        object of the admin user, with extended fields, and that {uid}        is both the {user_uid} of the admin user, and the {cust_uid} of        the customer, and will match up as such in other api structures.    -   Assign Meter to Customer [general]    -   Assigns or removes a meter to/from a customer.    -   Update Customer Info    -   Updates the configurable customer info fields, including:        -   Company name        -   Company contact (first/last)        -   Company contact email        -   Company contact phone    -   Delete Customer    -   Deletes the customer, and all their facilities, from the system.    -   Enable/Disable User    -   Enables/Disables the ability for a user to login. When disabled,        a user will be presented with an account disabled page.    -   Modify User Roles    -   Roles determine what a user is allowed to do. This adds and        removes a set of roles allowed by the specified user. Note, it        is added if it doesn't exist already. If a tag is not specified        to add, and the user already has that role, then it is not        removed from the user. Similar for remove.        -   ADMIN        -   ROLECREATOR        -   (custom)    -   Approve User    -   Updates the user settings by switching them from pending to        approved.    -   Add User    -   Adds the specified user from the system. Returns the new uid of        the user.    -   Delete User    -   Removes the specified user from the system.    -   Update User    -   Updates the user settings with the specified settings. If a        setting is not specified, it is not changed.        -   email        -   name        -   facilities access list    -   Reset User Password    -   Resets the user password.    -   Delete Facility    -   Deletes the specified facility. This will remove the facility        from each user access, and all meters at this facility will no        longer have an assigned facility.    -   Update Facility    -   Update the info for the specified facility. If a setting is not        specified, it is not changed.        -   name        -   address    -   Clear Meter Data    -   Clears all the log data for the specified meter and log.    -   Move Meter to Facility        -   Moves the meter to the specified facility, removing it from            a previous one if necessary.

The meter cloud system 600 includes a meter cloud user interface (UI)configured to enable a user to view, navigate, configure, and interactwith the various components of Meter Cloud. FIG. 31 illustrates anoverview of the meter cloud user interface in accordance with thepresent disclosure, where the various components will be describedbelow:

-   -   Login and Welcome: Entrance screen for the software. Allows the        user to login 1240, or create a new user. Once the user has        logged in, they are greeted with the Welcome Dashboard 1242,        which displays new information and links to all the major        functionality of the software.        -   Create User 1244: Allows the user to create a new User.            After entering user information, they are given the option            to create a new Customer, or to apply to join an existing            Customer, by entering that Customer's Key.        -   Login 1240: Allows an existing user to login to the Meter            Cloud UI.        -   Welcome Dashboard 1242: Once logged in, the Welcome            Dashboard 1242 displays useful information to the user, such            as their locations, summary dashboards, recent            notifications, and navigation options for other management            options.    -   Locations and Meters: Provides a list of the Locations and        Meters that are accessible by the Current User.        -   Locations 1246: Lists all the Locations (Facilities) that            are accessible by the Current User.        -   Meters 1248: Lists all the Meters which are available under            the selected Location.    -   Locations Management 1250        -   Allows Enterprise Users to configure Locations and Meters,            and search for new meters from the pool of unassigned ones.    -   User Configuration 1252        -   Allows a user to configure their own settings, such as            contact information.    -   Customer Management 1254: Allows the Owner User to configure        information about the Customer, including managing the list of        users for the Customer, editing the billing information, and        confirming pending users.        -   Customer Info: Configures the Customer Information, such as            Customer name, address, and provides the Customer Key for            distribution to prospective users.        -   Users 1256: Configures the list of users, including editing            the locations a user has access to, and removing users.        -   Billing 1258: Only accessible to the Customer Owner,            configures the billing information.        -   Pending Users 1260: Lists all users which are currently            pending, and gives an Enterprise User the ability to approve            or reject Pending Users.    -   Logs 1262: Displays log data for individual meters, including        both drilldown log specifics, and overview and analysis        dashboard displays.        -   Viewer 1264: Drilldown viewer for each of the individual            logs. Provides both spreadsheet views for raw data values,            and overview graphs.            -   Historical: The Historical Logs display trending data                for the various data channels the meter records, based                off of the time range and list of channels the user has                selected.                -   Spreadsheets: Displays each channel selected in a                    grid, with the rows as time, and the columns as each                    channel. Because there may be a disjoint in time                    between different channels, some channels may be                    empty at some times.                -   Graphs: Displays each channel selected on a combined                    graph, plotting time versus value.            -   Events                -   Limits                -   Digital Output                -   Digital Input                -   System Events            -   Power Quality                -   PQ                -   Displays a list of PQ events by time, and indicates                    if any waveforms are linked to the PQ event. If a                    waveform is linked, then the user can jump to that                    waveform by clicking on it.                -   Waveform                -   Displays a list of Waveform events by time and                    triggering channel. Selecting a waveform displays                    the samples graph and details of that waveform.                -   CBEMA                -   Displays a CBEMA graph of the PQ events, which plots                    magnitude vs duration. Selecting a PQ event on the                    graph provides information about the PQ Event, and                    jumps the user to that event in the PQ Event list.                -   EN50160                -   Links to the EN50160 Report.    -   Dashboards 1266: Overview dashboard for the log data, providing        quick glance graphs, summary values, and analyzed data views.        -   Log Overview: Provides overviews of each of the logs,            including trends of common historical channels, CBEMA curves            of PQ events, and counts of other events. The user can jump            to the relevant log by selecting the full view or history of            dashboard items.        -   Energy: Provides energy specific overviews and analysis,            such as usage by day or month, comparison by location, month            to month trends, and month to date usage.        -   Cost: Applies the Energy Billing cost configurations to            provide cost overviews, such as the rate breakdown for a            month, cost comparison between months, and month to date            costs.        -   Custom: Allows the user to create a dashboard template from            a set of dashboard types, such as trend, summary, or cost;            and configure a number of parameters, such as source            channels, meters, and time ranges; and add them to their            dashboard screen.    -   Energy Billing 1268: Configuration, dashboards, and reports        specific to providing the user with energy and cost management.        -   Configuration: Provides cost and rate structure            configuration for each location.        -   Linked Dashboards: Links the cost and energy dashboards into            one location.        -   Linked Reports: Links to the billing reports.    -   Reports 1270: Provides configuration and viewing for various        reports a user can create automatically for their meters and        locations.        -   Billing Reports        -   Log Exports        -   Custom Reports    -   Realtime Dashboard 1272: Provides a dashboard of (relatively)        live values from meters. The user can jump to the logs for        individual meters by selecting the history of any real time        channel (if available).        -   Meter View        -   Location View

In one embodiment, the UI works from a drill-down, single meter,viewpoint; however, in other embodiments, the UI operates from amulti-device point of view.

FIG. 32 is a block diagram illustrating physical components of acomputing device 1302, for example a client computing device (such asthe web browser client described above), a server (such as meter cloudserver 602), or any other computing device, with which examples of thepresent disclosure may be practiced. In a basic configuration, thecomputing device 1302 may include at least one processing unit 1304 anda system memory 1306. Depending on the configuration and type ofcomputing device, the system memory 1306 may comprise, but is notlimited to, volatile storage (e.g., random access memory), non-volatilestorage (e.g., read-only memory), flash memory, or any combination ofsuch memories. The system memory 1306 may include an operating system1307 and one or more program modules 1308 suitable for running softwareprograms/modules 1320 such as IO manager 1324, other utility 1326 andapplication 1328. As examples, system memory 1306 may store instructionsfor execution. Other examples of system memory 1306 may store dataassociated with applications. The operating system 1307, for example,may be suitable for controlling the operation of the computing device1302. Furthermore, examples of the present disclosure may be practicedin conjunction with a graphics library, other operating systems, or anyother application program and is not limited to any particularapplication or system. This basic configuration is illustrated in FIG.33 by those components within a dashed line 1322. The computing device1302 may have additional features or functionality. For example, thecomputing device 1302 may also include additional data storage devices(removable and/or non-removable) such as, for example, magnetic disks,optical disks, or tape. Such additional storage is illustrated in FIG.33 by a removable storage device 1309 and a non-removable storage device1310.

As stated above, a number of program modules and data files may bestored in the system memory 1306. While executing on the processing unit1304, program modules 1308 (e.g., Input/Output (I/O) manager 1324, otherutility 1326 and application 1328) may perform processes including, butnot limited to, one or more of the stages of the operations describedthroughout this disclosure. For example, program modules 1308 mayinclude energy billing module 1100, settings editor module 1102,internal log data module 1104, dashboard viewer module 1106, reportingmodule 1108, among others. Other program modules that may be used inaccordance with examples of the present disclosure may includeelectronic mail and contacts applications, word processing applications,spreadsheet applications, database applications, slide presentationapplications, drawing or computer-aided application programs, photoediting applications, authoring applications, etc.

Furthermore, examples of the present disclosure may be practiced in anelectrical circuit comprising discrete electronic elements, packaged orintegrated electronic chips containing logic gates, a circuit utilizinga microprocessor, or on a single chip containing electronic elements ormicroprocessors. For example, examples of the present disclosure may bepracticed via a system-on-a-chip (SOC) where each or many of thecomponents illustrated in FIG. 33 may be integrated onto a singleintegrated circuit. Such an SOC device may include one or moreprocessing units, graphics units, communications units, systemvirtualization units and various application functionality all of whichare integrated (or “burned”) onto the chip substrate as a singleintegrated circuit. When operating via an SOC, the functionalitydescribed herein may be operated via application-specific logicintegrated with other components of the computing device 1302 on thesingle integrated circuit (chip). Examples of the present disclosure mayalso be practiced using other technologies capable of performing logicaloperations such as, for example, AND, OR, and NOT, including but notlimited to mechanical, optical, fluidic, and quantum technologies. Inaddition, examples of the present disclosure may be practiced within ageneral purpose computer or in any other circuits or systems.

The computing device 1302 may also have one or more input device(s) 1312such as a keyboard, a mouse, a pen, a sound input device, a device forvoice input/recognition, a touch input device, etc. The output device(s)1314 such as a display, speakers, a printer, etc. may also be included.The aforementioned devices are examples and others may be used. Thecomputing device 1304 may include one or more communication connections1316 allowing communications with other computing devices 1318 and/ormeters/IEDs 1319. Examples of suitable communication connections 1316include, but are not limited to, a network interface card; RFtransmitter, receiver, and/or transceiver circuitry; universal serialbus (USB), parallel, and/or serial ports.

The term computer readable media as used herein may include computerstorage media. Computer storage media may include volatile andnonvolatile, removable and non-removable media implemented in any methodor technology for storage of information, such as computer readableinstructions, data structures, or program modules. The system memory1306, the removable storage device 1309, and the non-removable storagedevice 1310 are all computer storage media examples (i.e., memorystorage.) Computer storage media may include RAM, ROM, electricallyerasable read-only memory (EEPROM), flash memory or other memorytechnology, CD-ROM, digital versatile disks (DVD) or other opticalstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or any other article of manufacturewhich can be used to store information and which can be accessed by thecomputing device 1302. Any such computer storage media may be part ofthe computing device 1302. Computer storage media does not include acarrier wave or other propagated or modulated data signal.

Communication media may be embodied by computer readable instructions,data structures, program modules, or other data in a modulated datasignal, such as a carrier wave or other transport mechanism, andincludes any information delivery media. The term “modulated datasignal” may describe a signal that has one or more characteristics setor changed in such a manner as to encode information in the signal. Byway of example, and not limitation, communication media may includewired media such as a wired network or direct-wired connection, andwireless media such as acoustic, radio frequency (RF), infrared, andother wireless media.

It is to be appreciated that the computing device 1320 may, in certainembodiments, be a mobile computing device, for example, a mobiletelephone, a smart phone, a personal data assistant, a tablet personalcomputer, a phablet, a slate, a laptop computer, and the like, withwhich examples of the present disclosure may be practiced.

It is to be appreciated that the various features shown and describedare interchangeable, that is a feature shown in one embodiment may beincorporated into another embodiment.

While non-limiting embodiments are disclosed herein, many variations arepossible which remain within the concept and scope of the presentdisclosure. Such variations would become clear to one of ordinary skillin the art after inspection of the specification, drawings and claimsherein. The present disclosure therefore is not to be restricted exceptwithin the spirit and scope of the appended claims.

Furthermore, although the foregoing text sets forth a detaileddescription of numerous embodiments, it should be understood that thelegal scope of the present disclosure is defined by the words of theclaims set forth at the end of this patent. The detailed description isto be construed as exemplary only and does not describe every possibleembodiment, as describing every possible embodiment would beimpractical, if not impossible. One could implement numerous alternateembodiments, using either current technology or technology developedafter the filing date of this patent, which would still fall within thescope of the claims.

It should also be understood that, unless a term is expressly defined inthis patent using the sentence “As used herein, the term ‘______’ ishereby defined to mean . . . ” or a similar sentence, there is no intentto limit the meaning of that term, either expressly or by implication,beyond its plain or ordinary meaning, and such term should not beinterpreted to be limited in scope based on any statement made in anysection of this patent (other than the language of the claims). To theextent that any term recited in the claims at the end of this patent isreferred to in this patent in a manner consistent with a single meaning,that is done for sake of clarity only so as to not confuse the reader,and it is not intended that such claim term be limited, by implicationor otherwise, to that single meaning. Finally, unless a claim element isdefined by reciting the word “means” and a function without the recitalof any structure, it is not intended that the scope of any claim elementbe interpreted based on the application of 35 U.S.C. § 112, sixthparagraph.

What is claimed is:
 1. A cloud-based meter management system comprising:at least one meter manager module that collects meter log data from atleast one meter and sends the collected meter log data to at least oneserver via a predetermined format; the at least one server receives andstores the collected meter log data from the at least one meter managermodule; and at least one client device that accesses the at least oneserver to view the meter log data.
 2. The system as in claim 1, furthercomprising at least one network enabled meter that sends meter log datato the at least one server via the predetermined format.
 3. The systemas in claim 1, wherein the predetermined format is JSON data format. 4.The system as in claim 1, wherein the predetermined format is at leastof a XML and/or HTML.
 5. The system as in claim 1, wherein the at leastone server includes a web server for providing a user interface to theat least one client device.
 6. The system as in claim 1, wherein the atleast one server includes at least one REST web service that receives atleast one request from the at least one client device and provide aresponse to the at least one request.
 7. The system as in claim 6,wherein the at least one REST web service further receives the collectedmeter log data from the at least one meter manager module for storage inat least one database.
 8. The system as in claim 7, wherein the at leastone server is configured for autoscaling to add at least one additionalserver when an increased load of data sent to the at least one serverexceeds a predetermined limit.
 9. The system as in claim 8, furthercomprising at least one load balancer for distributing the sent dataamong the at least one server and the at least one additional server.10. The system as in claim 7, further comprising a message broker forrouting communications between the at least one web server, the at leastREST web service and the at least one database.
 11. The system as inclaim 10, further comprising at least one consumer that performs atleast one of collecting calls from the at least one REST web service,sending the calls to the at least one database and/or returning datafrom the at least one database.
 12. The system as in claim 11, whereinthe at least one consumer includes a push consumer that captures sentdata from the message broker and stores the sent data in the at leastone database.
 13. The system as in claim 12, wherein at least oneconsumer includes a metadata consumer that receives at least one requestfrom the message broker, sends the at least one request to the at leastone database and sends at least one response for presentation on a website hosted by the at least one server.
 14. The system as in claim 6,wherein the at least one server generates a key upon registration of auser, wherein the generated key is associated to the at least one meterof the registered user.
 15. The system as in claim 14, wherein the atleast one server verifies the sent data received from the at least onemeter via the generated key.
 16. The system as in claim 6, wherein theat least one server determines if the sent meter log data from the atleast one meter manager module exceeds a predetermined limit and, if thepredetermined limit is exceeded, the at least one server excludes thedata from being stored in the at least one database.
 17. The system asin claim 16, wherein the at least one server records a count andassociated time of day when the data was excluded.
 18. The system as inclaim 17, wherein the at least one server presents the count andassociated time of day of the excluded data to at least one user via aweb page.
 19. The system as in claim 1, wherein the meter log dataincludes waveform data, the waveform data including at least one ofTrigger Cause, Trigger Time, Recording Start Time, Time per sample,Total duration, Samples per cycle, List of samples per channel and/orList of RMS values for the cycle at the time of the trigger, and the atleast one server is further configured send a single waveform recordingto the at least one client device in response to a query.
 20. Acloud-based meter management system comprising: at least one web serviceenabled meter that pushes meter log data to at least one server via apredetermined format; at least one meter manager module that collectsmeter log data from at least one non-web service meter and pushes thecollected meter log data to the at least one server via thepredetermined format; the at least one server receives and stores pushedmeter log data from the at least one web service enabled meter and thecollected meter log data from the at least one meter manager module; andat least one client device that accesses the at least one server to viewthe meter log data.